Implementation guide

Overview

Implementing Jira Integration+ effectively from the beginning maximizes its value in your workspaces.

On this page: 1 Overview 1.1 Current State and Success Criteria 1.2 Set Up a Sandbox/Test Account 1.3 Get Started with the App 1.4 Configure Access and Permissions 1.5 Plan Your Roll-out 1.6 Training and Communication

On this page: 1 Overview 1.1 Current State and Success Criteria 1.2 Set Up a Sandbox/Test Account 1.3 Get Started with the App 1.4 Configure Access and Permissions 1.5 Plan Your Roll-out 1.6 Training and Communication

Existing Integrations: Identify any existing Slack–Jira integrations.
Define Success: Use metrics such as time saved, user satisfaction, reduction in Jira emails, and issues created from Slack.
Timeline: Establish a timeline and identify key stakeholders.
Connections: Determine the number of Slack workspaces and Jira instances you’ll connect.
Approval Process: Confirm any approvals required for adding bots or connecting with Jira.

Setting up a sandbox account lets you test and validate the app in a safe environment.

Create or access a sandbox workspace in Slack.
Add the app to the correct Slack workspace.
Connect the bot to Jira (you can use a Jira sandbox if available).
Run initial tests:
- Create a Jira ticket from Slack.
- Comment on Jira tickets from Slack.
- Transition or assign Jira tickets from Slack.
- Schedule Jira notifications in Slack.

Contact us with your bot ID for a free non-production license.

After connecting, explore the Slack-first interface for Jira. See our How-to Guide for more information.

Adjust access levels as needed, beyond the default Jira permissions.

Account Types:
- End User: Connects Slack and Jira accounts and inherits Jira permissions.
- Channel Administrator: Manages channel-specific configurations.
- System Administrator: Manages global settings and configurations.

Key Considerations:

Jira permissions are automatically enforced with Jira Integration+.
For most cases, keep channel configurations open for easier management.
Limit admin access as needed; add yourself as a user before saving.
Avoid configuring Jira Service Management and non-JSM projects simultaneously to prevent permission conflicts.

Adjust global settings during setup to fit your workflows.

Define initial workspaces, channels, and users for the roll-out.

Announce the Bot: Let users know the bot is available, so they can add it and receive notifications.
Integrate Channels: Identify channels where bot features, such as scheduled reports, can improve collaboration.

Training: Schedule a session to review Jira Integration+ features with our team.
Communication: Use your organization’s preferred channels to announce the launch, such as email, Slack, newsletters, or intranets. For Slack, we recommend using Block Kit for more engaging messages.