10X: Jira Data Synchronization

Data is mapped automatically between Jira Software and Jira Align during the synchronization process. In the event of Jira downtime, the Jira connector determines the last time a Jira project key and issue type combination was triggered and defines a lookback timer for each project and issue type.  The connector then updates or creates work items in Jira Align based on all corresponding Jira Software issues so that no cleanup is needed.

10X_Beta_JIRA_Data_Synchronization__115000088393__JIRA_data_sync.png

Jira Project becomes Jira Align Program Backlog

All work items from the Jira Project are mapped to a Program in Jira Align. One or more Jira Projects may be mapped to the same program in Jira Align, thereby creating a complete program backlog of all work items for a train.

Jira Agile Board becomes Jira Align Team

Field

Create

Update

AC to Jira

Jira to JA

JA to Jira

Jira to JA

Name

 

Yes

 

 

 

Jira User becomes Jira Align User*

Field

Create

Update

JA to Jira

Jira to JA

JA to Jira

Jira to JA

First Name

 

Yes

 

Yes

Last Name

 

Yes

 

Yes

Email

 

Yes

 

Yes

Assigned Team

Yes

Yes

Yes

Yes

Assigned Sprint

 

Yes

 

Yes


* Jira Software users are created in Jira Align when they own work items within Jira Software projects mapped to an Jira Align program. If the work item is assigned to a sprint in Jira Software and the Jira Align setting Allow Jira to add users to team if they belong to an issue is set to Yes, the user will also be assigned to a team in Jira Align. If those two conditions are not met, the user will be created but not assigned to a team.

If users are already assigned to an Agile team with a selected role in Jira Align, they will be assigned to that role on the Jira Align sprint's Members tab. If users are not already assigned to a team, they will be assigned to the team and sprint with the default role for the environment set in Jira Align under Administration > Jira Settings > Jira Setup.
 

Jira Software Fix Version becomes Release Vehicle in Jira Align

Field

Create

Update

JA to Jira*

Jira to JA

JA to Jira*

Jira to JA

Name

Yes

Yes

Yes

Yes

Start Date

Yes

Yes

Yes

Yes

End Date

Yes

Yes

Yes

Yes

Status**

Yes

Yes

Yes

Yes

Health

Yes

Yes

Yes

Yes


* The Jira Align Release Vehicle to Jira Software Fix Version sync does not remove Fix Versions from Jira Software Issues (epics, stories, and bugs), it only adds them.

** Fix Version to Release Vehicle sync:

  • Jira Projects are associated to Jira Align Programs.  Jira Fix Versions are associated to Jira Projects.  Jira Align will associate a newly created Release Vehicle to the Jira Align Program Increment that's Start Date and End Date range contains the Jira Fix Version's Release Date
  • Jira Fix Versions will not sync with Jira Align if their Release Date is not populated and the Release Date does not fall within the Start Date and End Date of an associated Program Increment
  • Start dates are synced when a Fix Version is created
  • ReleaseDate is synced to Ship Date
  • A Release Vehicle is set to Launched when a Fix Version is set to Released
  • Jira Align Go Live Date is removed when a Fix Version is set to Unreleased
  • Release Vehicle state is set to In Progress when a Fix Version is set to Unreleased
  • The order in which Jira Fix Versions sync with Jira Align Release Vehicles and work items sync to Jira Align will be important.  If a Jira issue syncs to a Jira Align work item prior to the Jira Fix Version to Jira Align Release Vehicle sync occurring there will need to be a subsequent update to the issue in Jira or a JQL Query ran in Jira Align against the issue(s) in order to populate the Fix Version.  For this reason, it is recommended to set the Release Date on Jira Fix Versions before associating a Fix Version to issues. 

Release Vehicle to Fix Version sync (on initial creation):

  • On the Release Vehicle create screen a selection of a Program Increment associated to a Jira Align Program that is associated to a Jira Project will render a Jira Project Field on the Release Vehicle.  This field is only accessible on the Release Vehicle create screen and will create a corresponding Fix Version in Jira when selected.
  • A Fix Version is set to Released when a Release Vehicle is set to Launched
  • A Fix Version Release Date is set to today's date when a Release Vehicle is set to Launched
  • A Fix Version is set to Unreleased when a Release Vehicle is set to In Progress or Not Started

Jira Software Sprint becomes Sprint in Jira Align

Field

Create

Update

JA to Jira

Jira to JA

JA to Jira

Jira to JA

Name

 

Yes

 

Yes

End Date

 

Yes

 

Yes

 

Jira Software Epic becomes Feature in Jira Align

Field

Create

Update

JA to Jira

Jira to JA

JA to Jira

Jira to JA

Name (Jira Epic Name)

Yes

Yes

Yes

Yes

Summary

Yes

Yes

Yes

Yes

Description*

Yes

Yes

Yes

Yes

Estimate (Points)

Yes

Yes

Yes

Yes

Acceptance Criteria*

Yes

Yes

Yes

Yes

Owner (Jira Assignee)**

Yes

Yes

Yes

Yes

Status***

Yes

Yes

Yes

Yes

Program Increment*****

Yes

Yes

Yes

Yes

Tags******

Yes

Yes

Yes

Yes


* the field supports a rich text editor. Rich text editor support between Jira Align and Jira Server or Data Center works with HTML plug-ins only and will not work with plug-ins that use a customized wiki markup. In addition, the mapped Jira fields must be configured to use the plugin's render. Rich text editor support is not currently supported with Jira Cloud (users must sync plain text).

** the following applies when you consolidated the Create and Edit Jira Software screens. If the Jira Align Owner field is populated but the Reporter field does not exist in Jira Software, the sync will fail. If the Reporter field does not exist in Jira Software and the Jira Align Owner field is not populated, the sync will be successful because the connector skips the mapping.

*** the comments section in Jira Software is updated with details and the issue is transitioned

***** from Jira Software Fix Version applied

****** spaces in tags are replaced with an underscore as Jira Software labels do not support spaces. The tags with a “j:” prefix in Jira Align are generated by the Jira connector by default. These are tags for the issue key, fix version name, and sprint name. The tags with a “j:” prefix will not sync from Jira Align to Jira Software.

If a feature is pushed to multiple Jira Software projects from Jira Align, then the fields on the feature synchronize one way from Jira Align to Jira Software, with the exception that child stories assigned to the Jira Software epic will still roll up to the same feature in Jira Align.

Jira Software Story and Configured Custom Issue Types become Stories in Jira Align

Field

Create

Update

JA to Jira

Jira to JA

JA to Jira

Jira to JA

Name (Jira Summary)

Yes

Yes

Yes

Yes

Description*

Yes

Yes

Yes

Yes

Estimate (Points)**

Yes

Yes

Yes

Yes

Assigned Team

Yes

Yes

Yes

Yes

Assigned Sprint

Yes

Yes

Yes

Yes

Parent Feature

Yes

Yes

Yes

Yes

Acceptance Criteria*

Yes

Yes

Yes

Yes

Assigned (Jira Assignee)

Yes

Yes

Yes

Yes

Status***

Yes

Yes

Yes

Yes

Release Vehicle

Yes

Yes

Yes

Yes

Program Increment*****

No

Yes

No

Yes

Type******

 

Yes

 

N/A

Tags*******

Yes

Yes

Yes

Yes


* the field supports a rich text editor. Rich text editor support between Jira Align and Jira Software works with HTML plug-ins only and will not work with plug-ins that use a customized wiki markup.

** points from Jira Software are visible and can be used when synced from Jira Software even if the particular Points value is not available in Jira Align. For estimating stories, Jira Align uses Modified Fibonacci or Power of Two. The point values from Jira Software are converted to time (Team Weeks or Member Weeks) according to the Monte Carlo settings (Administration > Settings > Platform > Portfolio). If you change the Jira Software-specific points value to a different value in Jira Align, the Jira Software-specific point value will disappear as an option from the Effort Points drop-down menu. All changes are saved in the audit log.

*** the comments section in Jira Software is updated with details and the issue is transitioned

***** from Jira Software Fix Version applied with the latest date; sprint overrides if conflict

****** set to a configured value for custom issue types

******* spaces in tags are replaced with an underscore as Jira Software labels do not support spaces. The tags with a “j:” prefix in Jira Align are generated by the Jira connector by default. These are tags for the issue key, fix version name, and sprint name. The tags with a “j:” prefix will not sync from Jira Align to Jira Software.

Jira Software Sub-Task or Task* becomes Task under Jira Align Story

Field

Create

Update

JA to Jira

Jira to JA

JA to Jira

Jira to JA

Name (Jira Summary)

Yes

Yes

Yes

Yes

Description

Yes

Yes

Yes

Yes

Estimate (Hours)

Yes

Yes

Yes

Yes

Hours Spent

 

Yes

 

Yes

Assigned

Yes

Yes

Yes

Yes

Status

 

Yes

 

Yes

Parent Story

 

Yes

 

Yes


* Users may choose to map either Tasks or Sub-Tasks from Jira Software to become Jira Align Tasks.  Traditionally our customers map Sub-Tasks from Jira to the Jira Align Task.  If Jira Tasks are to be mapped to Jira Align Tasks a custom link that connects the Jira Stories to the Jira Sub-Tasks will need to be configured under Jira Align Admin > Jira Settings > Manage Custom Fields. If customers choose to not map Jira Tasks to Jira Align Tasks they will still have the option of mapping Jira Tasks to Jira Align Stories of Type Task.

Additional notes on task synchronization:

  • If sub-tasks exist in Jira and are parented to a story that syncs to Jira Align, all of the sub-tasks will sync to Jira Align, regardless of whether task synchronization has been configured in Jira Settings. This is to support roll-up reporting of the stories.
  • Configuring task synchronization in Jira Settings identifies the sub-task issue type for tasks to be created in Jira as (when tasks are created in Jira Align and then sync to Jira). 
  • If a story has time logged against it in Jira Software, Jira Align will automatically create a child task on the corresponding Jira Align story with the same name as the Jira story, regardless of if task synchronization has been configured. This is to support roll-up reporting of the stories.

 

Jira Software Bug becomes Defect in Jira Align

Field

Create

Update

JA to Jira

Jira to JA

JA to Jira

Jira to JA

Name (Jira Summary)

 Yes

 Yes

 Yes

 Yes

Description*

 Yes

 Yes

 Yes

 Yes

Estimate (Points)**

 Yes

 Yes

 Yes

 Yes

Assigned Team

 Yes

 Yes

 Yes

 Yes

Assigned Sprint

 Yes

 Yes

 Yes

 Yes

Assigned (Jira Assignee)

 Yes

 Yes

 Yes

 Yes

Priority***

 Yes

 Yes

 Yes

 Yes

Status

 Yes

 Yes

 Yes

 Yes

State

 Yes

 Yes

 Yes

 Yes

Release Vehicle****

 Yes

 Yes

 Yes

 Yes

Tags***

Yes Yes Yes Yes

Program Increment******

 No

 Yes

 No

 Yes

 

* the field supports a rich text editor. Rich text editor support between Jira Align and Jira Software works with HTML plug-ins only and will not work with plug-ins that use a customized wiki markup.

** points from Jira Software are visible and can be used when synced from Jira Software even if the particular Points value is not available in Jira Align. For estimating stories, Jira Align uses Modified Fibonacci or Power of Two. The point values from Jira Software are converted to time (Team Weeks or Member Weeks) according to the Monte Carlo settings (Administration > Settings > Platform > Portfolio). If you change the Jira Software-specific points value to a different value in Jira Align, the Jira Software-specific point value will disappear as an option from the Effort Points drop-down menu. All changes are saved in the audit log.

*** priority can be mapped through Manage Custom Fields. If a priority value is not mapped, and then synced from Jira Software, Jira Align will set the priority to Normal.

**** syncs with Fix Version in Jira Software

****** from Jira Software Fix Version applied with the latest date; sprint overrides if conflict

******* spaces in tags are replaced with an underscore as Jira Software labels do not support spaces. The tags with a “j:” prefix in Jira Align are generated by the Jira connector by default. These are tags for the issue key, fix version name, and sprint name. The tags with a “j:” prefix will not sync from Jira Align to Jira Software.

Was this article helpful?
1 out of 1 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.