Story team assignment Between Jira Software and Jira Align using Select List (Cascading)

[#1]

To ensure a smooth workflow between Jira Software and Jira Align, it is important to sync the team field for different issue types, such as Features, Defects, Tasks, and Stories to better track the teamwork and progress

In this article, we will explore the process of syncing multiple teams from Jira Software to Jira Align, focusing on the Story issue type, providing step-by-step instructions on how to implement it effectively

Story Issue type sync

The Jira Align Story issue type syncs bi-directionally with the Jira Software story issue type. The team field on the Jira Align story syncs in one of two ways:

• Team boards in Jira Software are configured on one integrated team board per a project basis with a correctly established filter share

• Custom team mappings configured under Jira Align Admin > Jira Settings > Manage Custom Fields

Team Mapping Scenarios

One Jira Project and One Team x One Program and One Team in Jira Align

If you want to sync single teams from Jira to Jira Align, please check out the community article Syncing the Team Field Between Jira Software and Jira Align

Alternatively, suppose more than one team needs to be synced to the same program in Jira Align. In that case, the custom field sync can resolve and manage the team assignments by matching the dropdown field values in Jira to the corresponding assigned team in Jira Align. Check in the table below the assignment selection x team assignment results

Check in the table below the assignment selection and their team assignment results

Story team selection Type in Jira	JA team Mapping Under Administration > Jira Settings > Jira Setup > Team custom field in Jira Aling	Resulting Behavior in Jira Align
Selecting both values (parent and child value) in Jira Story e.g.:	Both team values (Parent and Child) are mapped	The story will be assigned to the "Child Team Value 1" team in JA. If JA team is mapped to ‘Select one’ the Story will sync and be assigned to 'Unassigned ' team
Selecting only parent value e.g.:	Both team values (Parent and Child) are mapped	The story will be assigned to the "Child Team Value 1" team in JA
Selecting a non-JA mapped child team value e.g.: Child team 2 (only exists in Jira)	Only Parent-team value mapped	The story will be assigned to the first mapped/listed JA team Under Administration > Jira Settings > Jira Setup > Team custom field in Jira Aling

• In case of a conflict of data, the JA custom field mapped team will overwrite the board team mapping (Under Administration > Jira Management > Jira Boards)

How-to

If you desire to achieve one or more of the scenarios described above, please follow the steps listed below:

Jira Software custom field configuration:

1. Navigate to the Jira Software Settings > click on Issues 

2. Under Fields, click on Custom Fields; in the upper right, click on 'Create custom field' and configure as follows

3. Field type: Select List (Cascading)

4. Name* (required field) = Custom field name

5. Navigate back to Fields and access Custom Fields

6. Search for the created field, and under the menu, click on 'Context and default value' and set the default values for parent and child values and also the screens (Stories)

Once the Jira Software configuration is complete, it is time to put the teams in Jira Align

Under Administration > Jira Settings > Jira Setup > Team custom field

1. Select the "Jira Project" to be mapped

2. Select "Custom Field Type" as "Dropdown"

3. Dropdown Custom Field ID: ID of the custom field in Jira
   how to: How to find any custom field's IDs | Jira | Atlassian Documentation

4. Jira Team Value = Should match the first dropdown name in Jira, aka "Organizations."

5. Child Team Value = Should match the second dropdown name in Jira, aka "Team."

6. Jira Align Team = Jira Align team that will be mapped

When configured, the Jira Align configuration should look like the screenshot below