How can we help you?

The AgilityHealth integration with Jira allows Company Admins to sync teams in AgilityHealth to projects and boards in Jira Cloud or Jira Data Center. Once set up, teams can sync team growth items to their board and manage them in Jira, along with their planned work. Additionally, performance metrics for the team can be synced from Jira to AgilityHealth and used to populate widgets on the 4 Lenz Dashboard. Also, some assessment questions can be auto-populated with answers as they relate to Jira data.

Check out the below demo video for a quick overview.

You can also find AgilityHealth in the Atlassian Marketplace.

Add Connection, Manage Instances, and Manage Linked Teams

A Company Admin for your company will need to create the connection between AgilityHealth and the version of Jira your company uses. In the Settings area of AgilityHealth, visit Manage Integrations and then click the Link button for either Jira Cloud or Jira Data Center to add a connection. If a Manage button is visible, a connection has already been established.

After clicking the Link button, credentials will need to be entered for the version of Jira you are connecting to. This information only needs to be entered one time - once an instance is linked, you can easily add other instances without reauthenticating the connection.

Jira Cloud:

Jira Data Center:

For Jira Data Center, you can use either token-based authentication or credential-based authentication.

Following authentication, you will be taken to the Link Team page where you can add or delete instances that are connected to AgilityHealth and link or unlink teams in AgilityHealth to the projects and boards in your Jira instances.

An instance has been added and two AgilityHealth Teams have been linked to two Jira Projects and Boards in the example below:

Use the Add New Instance or Delete Instance button to add or remove instances.

From the dropdowns in each field, select the instance, project, board, and AgilityHealth Team, and then click the Link button to enable growth item syncing and pull in performance metrics for that team.

Bulk Import and Export

The Bulk Link button is available to bulk import and link multiple teams in AgilityHealth to their Jira boards and projects for one Jira instance at a time.

Choose the 'Download Template' option to download an Excel template to be used for importing your data. Fill out the template completely, save your changes, and then select the 'Import' option. 

Bulk importing needs to be done for one instance at a time so be sure to select the correct instance from the Jira Instance dropdown before beginning. 

Once you select 'Import', the Import modal will open. Be sure to read the instructions, then click 'Upload' to import your file. 

If there are errors in the data, no data will import. An error log will populate in the modal and list all the errors that need to be corrected before you can import your file again. You can download those errors, if you wish.

If you'd like to export an Excel file of all your linked projects/boards/teams, select an instance from the Jira Instance dropdown, then choose the Export option under Bulk Link. 

For a step-by-step guide on using the template, visit this page.

Value Mapping

Be sure to review the Mapping tab. On this tab, you'll be able to customize for each instance the values mapped between AgilityHealth and Jira.

• By default, AgilityHealth will look at Epics in Jira to gather data for performance metrics such as feature cycle time and feature throughput.
• We will also by default map growth items that teams choose to sync from AgilityHealth to Stories in Jira.
  • You can create a custom label that will display in Jira for synced growth items using the Label field (be sure not to enter spaces in this field). We recommend an easily identifiable label such as AHGrowthItem.
• In the AgilityHealth Fields section, you can see what fields from a growth item in AgilityHealth will be synced to fields in Jira.
  • If you'd like to edit the Priority mapping, you can use the Map Values button to adjust these. Here are the default mapping values:

• Be sure to click Save to activate your changes.

Growth Items Sync

Once the Company Admin has linked AgilityHealth teams to the corresponding team board in Jira, team members can easily sync growth items with the category of Team created in their retrospectives or from their team's growth item dashboard to their Jira board.

Growth items can then be managed in the team's Jira board, along with their stories and tasks. Updates made in Jira to these growth items will be synced back to AgilityHealth automatically. 

Below, you can see on a team's assessment results page the Sync and Unsync buttons in the row of team growth items that are available to sync to Jira. The Sync Committed Items button will sync all team growth items with the status of Committed to Jira simultaneously. Once growth items are synced, information from the Jira board will show in the External Status, External ID and Issue Key columns. The Refresh button will update the sync between AgilityHealth and Jira.

The same options are available on the team's Growth Item dashboard as well. 

Mapped Fields:

When a growth item is synced to Jira, the following fields are mapped. This is a two-way sync for most fields but Status can only be updated in Jira, once a growth item has been synced. 

• Title to Title/Summary
• Description to Description
• Created date to Created
• Owner to Assignee
• Status to Status
• Priority to Priority

Status:

Here is how the status of a growth item is mapped between AgilityHealth and Jira. Once a growth item has been synced to Jira, the status can only be updated in Jira.

• Not Started maps to To Do in Jira
• Committed maps to To Do in Jira
• In Progress maps to In Progress in Jira
• Canceled maps to Done in Jira
• On Hold maps to To Do in Jira
• Done maps to Done in Jira

Priority:

The mapping for the values assigned to Priority can be adjusted for each instance of Jira by a Company Admin on the Mapping tab in Manage Integrations. By default, here are the mapped values:

Team Metrics

Once a team is linked to their Jira board, Iteration Data, Release Data, and Performance Metrics such as feature cycle time, feature throughput, deployment frequency, predictability, and defect ratio, can be pulled directly into AgilityHealth and displayed on the team's Metrics tab. When the 4 Lenz Dashboard is enabled for your company, the team's metrics will be pulled into that dashboard to populate most of the widgets.

There are a few conditions that need to be met to pull in this data. They are:

• A release must have issues/work items that are completed
• Issues/work items must be part of a completed sprint
• Only releases within the last 6 months are pulled
• The release date must be after the sprint end date

Company Admins can access these metrics from the Link Teams tab in the Manage Integrations section of Settings by clicking the name of the team in the AgilityHealth Team column.

Admins with user permissions to edit a team can access these metrics, from the Teams Dashboard. Locate the team and click the blue pencil Edit icon for the team. Once on the Team Profile tab, click on the Metrics tab, and the Iteration, Release Data/Increment, and Performance Metrics Data tables will then be seen. To refresh the data, click the Get Data button. This will take a few minutes so you can leave this page and return later. 

Auto-Populate Assessment Question Answers

Once teams have been linked to their Jira boards, some assessment questions can be answered for them in certain assessments. Currently, this functionality is available for our TeamHealth 3.0 and 4.0 assessments and the answers can be auto-populated for many of our Performance Metrics questions for Product Owners and Scrum Masters. 

To begin, you'll need to edit the team from the Teams Dashboard and go to their Metrics tab (as described in the previous section). Click the "Get Data" button and refresh the page to ensure data has populated with today's date in the Performance Measurements section of the Metrics tab. 

At this time, the 5 metrics we can carry over from this tab to the TeamHealth 3.0 assessment in the Performance dimension are:

• Deployment Frequency
• Defect Ratio
• Predictability
• Feature Cycle Time
• Feature Throughput

For the TeamHealth 4.0 assessment, we can carry over 6 metrics including:

• Predictability
• Deployment Frequency
• MTTR
• Defect Ratio
• Feature Cycle Time
• Story Cycle Time

Once the data has populated, you can create or launch an assessment for the TeamHealth Radar for this team. Product Owners and Scrum Masters will see answers populated for them for the questions related to these metrics (as long as they have been populated in the Performance Measurements section on the Metrics tab for the team first).

Product Owners and Scrum Masters can tell which questions have been auto-answered for them by noticing the score has been selected and either the Jira Cloud or Jira Data Center logo is in the upper right corner of the question on the assessment. 

The score can be changed manually by the Product Owner or Scrum Master if they disagree with the auto-population and that score will be reflected on the radar results page. 

When you click on a performance competency in the radar image on the radar results page that contains an auto-populated answer, the Jira Cloud or Jira Data Center logo will be displayed to the left of the score in the Competency Profile modal.

More enhancements are in development for our Jira integrations. Stay tuned for updates!