Stories created in Jira Kanban Boards are not assigned a Team in Jira Align

Still need help?

The Atlassian Community is here for you.

Ask the community


Summary

A story located in a Kanban Board in a Jira Project, where the Project and Board are both configured in the Jira Connector will not be assigned to a Team when that Story is created in Jira Align

Environment

Jira Align

Diagnosis

When using Sprint Teams in Jira, then the Stories created in Jira Align are assigned to Teams in Jira based on both:

  • The Board being configured in the Jira Management Page in Jira Align

  • The Sprints of the story are correctly configured to match with Anchor Sprints of the related Program Increment (PI).

As Kanban Boards don't use sprints the process to assign a Team to a story that has been synchronized from Jira is unable to set a Team using the Jira Management Configuration

Cause

Kanban Boards require a different configuration in order to assign a Team to a Story than is needed for Stories in Sprint Boards

Solution

To solve this problem, custom team fields need to be configured and this requires changes to be made in both Jira and Jira Align - expand the below sections to see the specific details:

1. Create a custom field in Jira for the team

(warning) Do not attempt to use the default Jira Team field for this. The default team field is of type Team and is not supported by the Jira Connector

(info) There should only be one team field per project - although a single field can be used across more than one project

(info) The Custom Team field mapping requires the Standard Select List (single choice) field type to be present on the Create and Edit screens of the Story issue type.

  1. Go to Jira Administration > Issues > Custom Fields

  2. Click "Add Custom Field" in the upper right corner of the Custom Fields page

  3. Select the Single-Choice list

  4. Type a name for the custom field 

  5. In the Options field, type the name of the team (or teams) that will appear as an option for the field (we recommend using the same team names in Jira and Jira Align) and click on Create

  6. On the list of screens, search for the Project or Screens that will be using the custom field and click to select all that apply

  7. After selecting them, click on 'Update' - located at the bottom of the list

  8. Then locate the new field in  the Custom Fields list and make a note of the numeric field ID

Once this is set up, all tickets created will have the field "Team" as optional or mandatory info depending on how you configure the field, however, if this data is not set on Jira side, it will not reflect on the Jira Align Side.

2. Relate the custom field in Jira to a Team in Jira Align

  1. Go to Jira Align Administration > Jira Settings > Jira Setup 

  2. Next to the 'Team custom field' setting, click on 'Configure'

  3. Scroll to locate the section called 'Sync Jira Team Values with Jira Align Teams

  4. Select the Jira project to which the Jira team that you want to synchronize belongs

  5. Leave custom field type set to Dropdown

  6. Type the custom team field value in the corresponding box (as noted in Step A:8 in the Jira section)  Use the following format: customfield_#####, where ##### is the team custom field ID in Jira - for example customfield_11012

  7. Under Sync Jira Team Values with Jira Align Teams, click Add New

  8. In the Jira Team Value box, type the name of the team in Jira that you want to synchronize. This must match exactly to the field's value for that team in Jira. As you are using a single-select field in Jira, the Child Team Value field should be left blank

  9. From the Jira Align Team drop-down menu, select the team in Jira Align with which you want to synchronize the Jira team

  10. Click Update Teams

  11. To add more teams, click repeat Steps 7–10

After configuring both Jira and Jira Align as above, the next synchronization of Jira to Jira Align should assign Teams to the Stories.

Related content


Last modified on Apr 24, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.