Jira Integration Cloud


Create Jira issues directly from Brightidea submissions! Transfer ideas for project management and implementation, or link ideas to existing issues for improved cross-system tracking. To get started, follow the guide below.

Important Note:

  1. This feature is currently in Beta development. Please speak to your Customer Success Manager if you would like to enable this functionality.
  2. You will need administrator access in both Brightidea and Jira to complete the initial system setup.
  3. This KBA is for if you are on the Cloud version of Jira, if you are on the On-Premise Jira version, refer to this KBA for instructions. Login to your Atlassian account settings to determine Cloud vs On-Premise.

 

Enabling the Jira Integration in Your Activity

Once the option is enabled, the Jira integration can be enabled in any Activity.

As a System or Activity Admin, navigate in the desired Activity to Site Setup > Ideas > Integrations.
mceclip0.png

  •  and save
  • By default the integration will be made available to admins in the Activity. To also allow end-user participants to use the integration, select 

Using the Integration to Create and Link Jira Issues

After Jira has been successfully connected and enabled in an Activity, Admins will have two different approaches to creating or linking issues from submissions:

  1. Admin-only workflow from pipeline Steps or List views
  2. Admin or end-user workflow from the View Idea page, which requires additional configuration below

From either approach, the first time creating an issue or link, each user will be prompted to authorize with their Jira accounts:

Screen_Shot_2020-06-26_at_1.27.45_PM.png

Connecting to Jira through Pipeline Steps/List View 

From the Actions menu or on left click on the idea, admins will see two new options in List and Steps views: (a) Create a new Jira issue from a submission or (b) Link a submission to an existing Jira issue.

Screen_Shot_2020-06-09_at_1.27.23_PM.png

Simply select a Submission, choose Create or Link from the Actions menu, and follow the dialogs:

Screen_Shot_2020-06-26_at_1.29.31_PM.png

mceclip3.png

 

Connecting Jira through View Idea

Using the Jira integration on View Idea requires setting up a widget. The visibility of the widget will be determined by your configuration in the prior step: Enabling the Jira Integration in Your Activity.

  1. Navigate to View Idea for any idea in the activity
  2. Enable widget editor mode from the floating gear button
  3. Select the Jira Issues widget and click the "+" button to add to the page
    • mceclip1.png
  4. Move and configure the widget as desired
  5. Refresh the page, you should now see the widget load properly:
    • mceclip2.png

If a user has not authorized, they will see a plain HTML link in the widget to any existing issues by their Jira key.

Authorized users will see a rich view of Jira issues with the issue type, title, and status displayed in line:

Screen_Shot_2020-06-26_at_2.31.34_PM.png

Issues can be unlinked by hovering over the issue icon and clicking "unlink."

 

General Behavior

  • Idea Title will be transferred for the Issue Summary
  • Idea Description will be transferred to the Issue Description
  • Issues will be created and linked on behalf of the acting user, and the account they have authorized
  • Access & visibility to Jira projects, issue types, and issues will adhere to that user's Jira permissions

Important Notes

  • The Jira instance must be visible to Brightidea for the two systems to communicate; firewalls and [virtual] networks may prevent this for on-premise installations. Check with your IT or Jira admins for more info.
  • At this time, Title/Subject and Description are the fields that are transferred to Jira
    • Required fields with no defaults in the Jira project may block submission from Brightidea
    • Additional fields will need to be manually copied as desired, once the issue is created
  • Not all rich text formatting can be transferred to Jira at this time. Brightidea uses underlying HTML formatting, and Jira has a specific markdown language that does not map 1:1
    • For example, certain formatting styles such as underline, strikethrough and ordered lists may not be parsed over correctly

  • Sub-task issue types are not currently supported
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments