You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Jira to Jira Align integration syncs the Team field between Jira Align and Jira Software on various work items (Jira Software Issues). The method of team synchronization depends on work item (issue type) and application setup.
Feature (Jira Software Epic): The Jira Align feature doesn't have a Team field, since Jira Align features are assigned to programs instead of directly to Agile teams. This means a team value won't sync from Jira Software to Jira Align at the feature (Jira Software Epic) level. If a custom team field is required on the Jira Epic Create Screen in Jira Software, the field won't be populated when initial creation occurs in Jira Align. This would lead to a connector sync error, resulting in the failure to create the issue in Jira Software. We recommend making any team field on the Jira Software Epic screen not required in Jira, or to manage all creation of Jira Software Epics in Jira Software.
Story: The Jira Align story syncs bi-directionally with the Jira Software story issue type. The team field on the Jira Align story syncs in one of two ways:
In Jira Software, projects consist of boards with filter queries to determine which issues will show on a board and filter shares to associate projects and groups to boards. To facilitate the Team field sync from Jira Software to Jira Align on stories, the Jira Integration will use a single project shared to a board's filter share to populate a project mapping for boards under Jira Align Admin > Jira Management. When there is only one integrated board for each integrated project between Jira Align and Jira Software, the connector will populate the Jira Align Team field based on this mapping. If there is more than one integrated board for an Integrated Project or the board has a No Project Found error, the connector won't be able to make this association and custom team mapping must be utilized to sync the Team field between Jira Software and Jira Align.
No Project Found errors will appear next to a board mapping on the Jira Align Admin > Jira Management page for one or more of the following reasons:
Custom Team field mapping is required in scenarios where there is more than one integrated board per a mapped project, or when the board owners don't want to adjust their board's filter share.
Jira Requirements and Setup for Custom Team Field Mapping:
The Custom Team field mapping requires the Standard Select List (single choice) field type from Jira Software, present on the Create and Edit screens of the Story issue type.
To create the custom field in Jira, click Jira Administration > Issues > Custom Fields and then click "Add Custom Field" in the upper right corner of the Custom Fields page.
Once the Custom Field has been created, please make sure the field is added to the Create and Edit screens of the Story Issue Type your Jira Instance.
NOTE - The Jira Integration does not support plugin or non-standard fields for the implementation of this custom field.
Jira Align Custom Team Field Mapping Setup:
To set up Custom Team field mapping in Jira Align, please follow the steps below.
Navigate to the Jira Align Administration > Jira Settings > Jira Setup panel:
Custom Type Stories:
Stories with custom types will sync bi-directionally between Jira Software and Jira Align. The Team field sync for these stories will adhere to the same logic as the Jira Software to Jira Align story Team field sync.
Defect (Jira Bug):
The Jira Software bug will sync bi-directionally between Jira Software and the Jira Align defect. The Team field sync will adhere to the same logic as the Jira Software to Jira Align story Team field sync.