Data is mapped automatically between Jira 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 issues so that no cleanup is needed.
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 |
||
|
JA 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 |
|
|
|
Yes |
|
Yes |
|
Assigned Team |
Yes |
Yes |
Yes |
Yes |
|
Assigned Sprint |
|
Yes |
|
Yes |
Additional notes on user synchronization:
- Updating user information doesn’t occur automatically, but is supported using the Pull Jira User Data process.
- Jira users are created in Jira Align when they own work items within Jira projects mapped to an Jira Align program. If the work item is assigned to a sprint in Jira 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 on the Jira Setup tab of the Jira Settings page.
|
Jira 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 |
No |
Yes |
|
Start Date |
Yes |
Yes |
Yes |
Yes |
|
End Date |
Yes |
Yes |
Yes |
Yes |
|
Status* |
Yes |
Yes |
Yes |
Yes |
|
Health |
Yes |
Yes |
Yes |
Yes |
Additional notes on release vehicle synchronization:
- The Jira Align release vehicle to Jira fix version sync does not remove fix versions from Jira Issues (epics, stories, and bugs), it only adds them.
* Fix version to release vehicle Status field sync:
- Jira projects are associated with Jira Align programs. Jira fix versions are associated with Jira projects. Jira Align will associate a newly created release vehicle to the Jira Align program increment whose 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.
- A release vehicle’s release date is synced to the fix version’s ship date.
- A release vehicle is set to Launched when a fix version is set to Released.
- The Jira Align Go Live Date is removed when a fix version is set to Unreleased.
- The release vehicle state is set to In Progress when a fix version is set to Unreleased.
-
The release vehicle state is set to Archived and health is set to Complete when a fix version is set to Archived. However, you cannot archive a release vehicle in Jira Align.
-
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 before the Jira fix version to Jira Align release vehicle sync occurs, 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 with issues.
Release vehicle to fix version sync (on initial creation):
- On the release vehicle create screen, a selection of a program increment associated with a Jira Align program that is associated with 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's 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 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 |
|
Goal |
|
Yes |
|
Yes |
| Jira Epic becomes Feature in Jira Align |
|||||
|
Field |
Create |
Update |
|
||
|
JA to Jira |
Jira to JA |
JA to Jira |
Jira to JA |
Notes | |
|
Name |
Yes |
Yes |
Yes |
Yes |
The Jira Cloud Epic Name field syncs with the Jira Align Jira Epic Name custom field. In Jira Server or Data Center, the Epic Name field syncs with the Jira Align feature’s Title field. |
|
Summary |
Yes |
Yes |
Yes |
Yes |
|
|
Description |
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). |
|
Estimate (Points) |
Yes |
Yes |
Yes |
Yes |
|
|
Parent Work Item (Epic or Capability) |
Yes |
No |
Yes |
No |
|
|
Acceptance Criteria |
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). |
|
Owner (Jira Assignee) |
Yes |
Yes |
Yes |
Yes |
The following applies when you consolidated the Create and Edit Jira screens. If the Jira Align Owner field is populated but the Reporter field does not exist in Jira, the sync will fail. If the Reporter field does not exist in Jira and the Jira Align Owner field is not populated, the sync will be successful because the connector skips the mapping. |
|
Status |
Yes |
Yes |
Yes |
Yes |
The comments section in Jira is updated with details and the issue is transitioned |
|
Program Increment |
Yes |
Yes |
Yes |
Yes |
Applied from Jira Fix Version |
|
Tags |
Yes |
Yes |
Yes |
Yes |
Spaces in tags are replaced with an underscore as Jira 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. Tags with a “j:” prefix will not sync from Jira Align to Jira. |
| Blocked |
Yes |
Yes |
Yes |
Yes |
|
|
Business driver |
Yes |
Yes |
Yes |
Yes |
|
|
Capitalized |
Yes |
Yes |
Yes |
Yes |
|
|
Category |
Yes |
Yes |
Yes |
Yes |
|
|
Type |
Yes |
Yes |
Yes |
Yes |
|
|
Priority |
Yes |
Yes |
Yes |
Yes |
|
|
Custom text input fields |
Yes |
Yes |
Yes |
Yes |
|
|
Custom single-select dropdown fields |
Yes |
Yes |
Yes |
Yes |
|
Additional notes on feature synchronization:
- If a feature is pushed to multiple Jira projects from Jira Align, then the fields on the feature synchronize one way from Jira Align to Jira, with the exception that child stories assigned to the Jira epic will still roll up to the same feature in Jira Align.
| Jira 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 |
Notes |
|
|
Name (Jira Summary) |
Yes |
Yes |
Yes |
Yes |
|
|
Description |
Yes |
Yes |
Yes |
Yes |
The field supports a rich text editor. Rich text editor support between Jira Align and Jira works with HTML plug-ins only and will not work with plug-ins that use a customized wiki markup. |
|
Estimate (Points) |
Yes |
Yes |
Yes |
Yes |
Points from Jira are visible and can be used when synced from Jira 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 are converted to time (Team Weeks or Member Weeks) according to the Estimation Conversions settings. If you change the Jira-specific points value to a different value in Jira Align, the Jira-specific point value will disappear as an option from the Effort Points drop-down menu. All changes are saved in the audit log. |
|
Assigned Team |
Yes |
Yes |
Yes |
Yes |
|
|
Assigned Sprint |
Yes |
Yes |
Yes |
Yes |
|
|
Parent Feature |
Yes |
Yes |
Yes |
Yes |
|
|
Acceptance Criteria |
Yes |
Yes |
Yes |
Yes |
The field supports a rich text editor. Rich text editor support between Jira Align and Jira works with HTML plug-ins only and will not work with plug-ins that use a customized wiki markup. |
|
Assigned (Jira Assignee) |
Yes |
Yes |
Yes |
Yes |
|
|
Status |
Yes |
Yes |
Yes |
Yes |
The comments section in Jira is updated with details and the issue is transitioned |
|
Release Vehicle |
Yes |
Yes |
Yes |
Yes |
|
|
Program Increment |
No |
Yes |
No |
Yes |
Applied from Jira Fix Version with the latest date; sprint overrides if conflict |
|
Type |
|
Yes |
|
N/A |
Set to a configured value for custom issue types |
|
Tags |
Yes |
Yes |
Yes |
Yes |
Spaces in tags are replaced with an underscore as Jira 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. Tags with a “j:” prefix will not sync from Jira Align to Jira. |
| Jira 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 |
Additional notes on task synchronization:
- Users may choose to map either Tasks or Sub-Tasks from Jira 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.
- 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, 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 Bug becomes Defect in Jira Align | |||||
|
Field |
Create |
Update |
|
||
|
JA to Jira |
Jira to JA |
JA to Jira |
Jira to JA |
Notes |
|
|
Name (Jira Summary) |
Yes |
Yes |
Yes |
Yes |
|
|
Description |
Yes |
Yes |
Yes |
Yes |
The field supports a rich text editor. Rich text editor support between Jira Align and Jira works with HTML plug-ins only and will not work with plug-ins that use a customized wiki markup. |
|
Estimate (Points) |
Yes |
Yes |
Yes |
Yes |
Points from Jira are visible and can be used when synced from Jira 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 are converted to time (Team Weeks or Member Weeks) according to the Estimation Conversions settings. If you change the Jira-specific points value to a different value in Jira Align, the Jira-specific point value will disappear as an option from the Effort Points drop-down menu. All changes are saved in the audit log. |
|
Assigned Team |
Yes |
Yes |
Yes |
Yes |
|
|
Assigned Sprint |
Yes |
Yes |
Yes |
Yes |
|
|
Assigned (Jira Assignee) |
Yes |
Yes |
Yes |
Yes |
|
|
Priority |
Yes |
Yes |
Yes |
Yes |
Priority can be mapped through Manage Custom Fields. If a priority value is not mapped, and then synced from Jira, Jira Align will set the priority to Normal. |
|
Status |
Yes |
Yes |
Yes |
Yes |
|
|
State |
Yes |
Yes |
Yes |
Yes |
|
|
Release Vehicle |
Yes |
Yes |
Yes |
Yes |
Syncs with fix version in Jira |
|
Tags |
Yes | Yes | Yes | Yes | Spaces in tags are replaced with an underscore as Jira 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. Tags with a “j:” prefix will not sync from Jira Align to Jira. |
|
Program Increment |
No |
Yes |
No |
Yes |
Applied from Jira Fix Version with the latest date; sprint overrides if conflict |
Print 
PDF
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.