Versions Compared

Old Version 9

changes.mady.by.user Michelle Ruoff

Saved on

compared with

New Version 10

changes.mady.by.user Megan Storie

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Ensuring a thorough implementation of

Overview

Implementing Jira Integration+ effectively from the beginning maximizes its value in your workspaces from the outset sets a strong foundation, enhancing the value derived from the platform right from the start.

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 and announcements.

  • Go-Live.

    • On this page:

    Table of Contents
    minLevel1
    maxLevel6
    outlinefalse
    styledisc
    typelist
    printabletrue

    Current

    state

    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

    Success Criteria

    • 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.

    Is there

    • Timeline: Establish 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

    • 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.

    Set Up a Sandbox/Test Account

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

    1. Create or access a sandbox workspace in Slack.

    2. Add our the app to Slack - make sure to add it to the correct Slack workspace in Slack.

    3. Follow Connect the connection process to connect your bot to Jira (you can use a Jira sandbox Jira here if you wantavailable).

      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 areRun initial tests:

      • Create a Jira ticket from Slack.

      • Comment on

      the

      • Jira

      ticket

      • tickets from Slack.

      Interact with

      • Transition or assign Jira tickets from Slack

      (transition or assign)

      • .

      • Schedule Jira notifications in Slack.

    Contact

    Us and provide

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

    Getting Started using our app

    Once your bot is connected, you can explore our Slack

    Get Started with the App

    After connecting, explore the Slack-first interface for Jira. Check out See our howHow-to -use sectionGuide for more information on using our app.

    Configure

    access

    Access and

    permissionsThese settings are optional to restrict access

    Permissions

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

    • Account

    types

    • Types:

      • End User

      - users of the system who connect their Slack accounts to their

      • : Connects Slack and Jira accounts and

      inherent

      • inherits 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

      • : Manages channel-specific configurations.

      • System Administrator

      - account admins who control

      • : Manages global settings and configurations.

    Things to consider when configuring access

    Key Considerations:

    We do not recommend

    • Jira permissions are always respected automatically enforced 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 Integration+.

    • For most cases, keep channel configurations open for easier management.

    • Limit admin access as needed; add yourself as a user before saving.

    • You can update your access settings in the account portal at any time.

    Info

    • Avoid configuring Jira Service Management

    projects

    • and non-JSM

    (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

    • to prevent permission conflicts.

    Adjust global settings during setup to fit your workflows.

    Plan Your Roll-out

    Define initial workspaces, channels, and users initially configured for your the 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:

    1. They announce 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 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

    • 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.

    Use our Channel Configuration Template to plan your channel rollout.

    Training and Communication

    • Training: Schedule a session to review Jira Integration+ features

    and functionality feel free to schedule time

    • with our team

    to review

    • .

    • Communication

    planEach 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

    • : 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.