Table of Contents


Nick Cron Updated by Nick Cron

Implementing Jira Integration+ in your workspace(s) the right way from the beginning is a great way to get started on the right path and increase the value you receive from the platform.

Process Overview

  1. Gather information on current state and define success
  2. Set up a sandbox account
  3. Try out our features
  4. Configure access and permissions
  5. Create workspace, channel, and configuration plan
  6. Training planning
  7. Communications & Announcements
  8. Go-Live

Current state and success criteria

  1. Is there an existing integration between Slack and Jira? If so, what integration is being used?
  2. How will you define success?
    1. Examples:
      1. Time saved in context switches
      2. User satisfaction and feedback
      3. Number of Jira emails converted to Slack messages
      4. Number of issues created from Slack
  3. Is there a specific timeline in mind for this project?
  4. What groups or individuals within your organization are involved, what role(s) does each person have?
  5. How many instances of Jira are you connecting to Slack?
  6. How many workspaces in Slack are you connecting to Jira?
  7. 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.

  1. Create a new workspace or login to an existing sandbox workspace in Slack.
  2. Add our app to Slack - make sure to add to the correct workspace in Slack.
  3. Follow the connection process to connect your bot to Jira (you can use a sandbox jira here if you want)
    1. We recommend using a Service Account as the main authorized user.
  4. Start your testing and validation. The basic test scenarios we recommend running at a minimum are:
    1. Create Jira ticket from Slack
    2. Comment on Jira ticket from Slack
    3. Interact with Jira tickets from Slack (transition or assign)
    4. Schedule Jira notifications in Slack
  5. 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 start to 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 if you want to restrict access beyond the default Jira permissions. Learn more

Account types

  • End User - users of the system who connect their Slack accounts to their Jira accounts and inherent Jira permissions. Learn more
  • Channel Administrator - global list of users who can manage configurations at the channel level for notifications, quick create, user override and other settings. Learn more
  • System Administrator - account admins who control global settings and configurations. Learn more

Things to consider when configuring access:

  • Jira permissions are always respected automatically with Jira integration+ and these setting allow further restrictions where required.
  • We suggest leaving 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.

Configure the global settings

There are a number of 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 suite your workflows.

Planning your roll-out

The next step in planning a deployment for your team is determining the workspaces, channels and users that will be initially configured for your roll-out. This process involves some 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:

  1. Announcing the bot's availability so users can add the App and receive personal notifications.
  2. 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 were scheduled reports would benefit the users? We created this google sheet your team can copy and utilize to plan your channel roll out:

Training and Communication Planning


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.

For end-user guides, the resources available are:

Communication Plan

Each organization has preferred communication channels with end users. Many customer 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 for the new solution.

Support Plan

Make sure top include in your communications how users will provide their feedback and ask questions of the account admins. If needing support from Nextup directly we can always be reached by emailing, or using the chat feature at


We're excited for Jira Integration+ to be live within your organization. A successful go-live should include includes the below (adjust for your organization).

  1. Install and configure Jira Integration+ in the production workspace. These will be the same steps you followed if you were able to test in a sandbox environment.
  2. Add the bot to the identified channels and configure channel notifications based on defined use cases.
  3. Send launch communications. This will prompt users to add the app and connect their Jira and Slack accounts so they can receive personal notifications from the bot.
  4. Monitor feedback and usage to see how Jira Integration+ helps your users!

How did we do?

Get in touch