Ensuring a thorough implementation of Jira Integration+ in your workspace(s) from the outset sets a strong foundation, enhancing the value derived from the platform right from the start.
On this page:
|
|---|
Process Overview
Gather information on the current state and define success.
Set up a sandbox account.
Try out our features.
Configure access and permissions.
Create a workspace, channel, and configuration plan.
Training planning.
Communications & Announcements.
Go-Live.
On this page:
|
|---|
Current state and success criteria
Is there an existing integration between Slack and Jira? If so, what integration is being used?
How will you define success?
Examples:
Time saved in context switches.
User satisfaction and feedback.
A number of Jira emails were converted to Slack messages.
Several issues were created from Slack.
Is there a specific timeline in mind for this project?
What groups or individuals within your organization are involved, and what role(s) does each person have?
How many instances of Jira are you connecting to Slack?
How many workspaces in Slack are you connecting to Jira?
Are approvals required to add new bots to Slack or connect with Jira? If so, who needs to approve?
Setting up a Sandbox / Test account
Creating a sandbox account is an easy way to get started understanding our app, and validating our product helps solve your use cases.
Create a new workspace or log into an existing sandbox workspace in Slack.
Add our app to Slack - make sure to add it to the correct workspace in Slack.
Follow the connection process to connect your bot to Jira (you can use a sandbox Jira here if you want).
We recommend using a Service Account as the main authorized user.
Start your testing and validation. The basic test scenarios we recommend running at a minimum are:
Create a Jira ticket from Slack.
Comment on the Jira ticket from Slack.
Interact with Jira tickets from Slack (transition or assign).
Schedule Jira notifications in Slack.
Contact Us and provide your bot ID for a free non-production license.
Getting Started using our app
Once your bot is connected, you can explore our Slack first interface for Jira. Check out our how-to-use section for more information on using our app.
Configure access and permissions
These settings are optional to restrict access beyond the default Jira permissions.
Account types
End User - users of the system who connect their Slack accounts to their Jira accounts and inherent Jira permissions.
Channel Administrator - a global list of users who can manage configurations at the channel level for notifications, quick create, user override, and other settings.
System Administrator - account admins who control global settings and configurations.
Things to consider when configuring access:
Jira permissions are always respected automatically with Jira integration+, and these settings allow further restrictions where required.
We suggest leaving the configuration of channels open in most cases.
You can review currently configured channels in the administration area at any time to view current configurations.
We recommend restricting admin access in most cases. Make sure to add yourself as a user before saving.
You can update your access settings in the account portal at any time.
| Info |
|---|
We do not recommend configuring Jira Service Management projects and non-JSM (e.g., Jira Core or Jira Software) projects simultaneously. While we will allow you to do so, permissions may not work correctly in Jira Service Management projects. |
Configure the global settings.
There are several settings that are configured by an administrator and apply to the account globally. On set-up, these are set by default to our most common settings, but you can review all the global settings to make adjustments that suit your workflows.
Planning your roll-out
The next step in planning a deployment for your team is determining the workspaces, channels, and users initially configured for your roll-out. This process involves investigation and planning based on your team and current state. Please adopt our suggested process as needed to fit your needs.
A launch consists of:
They announce the bot's availability so users can add the app and receive personal notifications.
Adding the bot to channels to assist users in team collaboration.
Identify channels to integrate
Are there any existing channels that would benefit from the bot's collaboration features? Are there channels where scheduled reports would benefit the users? We created this Google sheet your team can copy and utilize to plan your channel rollout:
Training and Communication Planning
Training
If you are an account admin and would like to review Jira Integration+ features and functionality feel free to schedule time with our team to review.
Communication Plan
Each organization has preferred communication channels with end users. Many customers choose to send a launch email accompanied by a message in a main Slack channel (we recommend using Slack Block Kit if available). Announcements in internal newsletters, intranets, or company updates can also help with awareness of the new solution.