If you differentiate your teams in Jira by a certain field (instead of Jira Project or Jira Sprint) you must follow this guide.
Requirements
The team field must be of one of the types shown in the dropdown. This includes:
label (customfield)
label (native)
components
select (customfield)
multi-select (customfield)
The sprints which are shared by the teams need to be created on a common board
Configuration steps
Configure Jira Team Mapping
Navigate to “ALM Connections“, edit your Jira connection, select the screen “Team Mapping“
Select a team to configure by clicking on “Edit“
Choose the Jira project in which the team is working
Hit “Show advanced settings“ on the top right of the page
Select the common board. This is the board on which the shared sprints are created on.
-> Do not select the board of the team itself. In the example blow, the “MLC board“ is the one on which the common sprints are created.
Enter the team-field definition. In the example below you can see the case when teams are identified by the components field.
Update (October 2024):
Team field values should now be entered as plain text, instead of JSON formatting.
If multiple values should be applied, they should be comma-separated
(eg. Value 1, Value 2)
Setup a new PI session
Configure a new piplanning session as usual
In the iterations screen, make sure that you select the same sprint for all the teams in one iteration. An example for Iteration PI1.1 can be seen bellow:
