Overview of Team Field Mapping on the ART Backlog Board
Team field mapping in piplanning.io enables the synchronisation of the specific field in your Jira Project/s that denotes Team ownership (assignment) of the ART Backlog work item.
For example, if a Team pulls a Feature from the ART Backlog, that Team value in piplanning.io can be synchronized with the appropriate field in Jira, and vice versa.
This article and the configuration for the Team field mapping applies only to the Sticky Notes on ART level boards (i.e. the ART level work items such as Features, Enablers, Epics, etc. synchronized with Jira)
Team field mapping for single ART sessions
Within your PI session configuration under Backlog Board you can find a separate Tab to do the team field mapping
Select your team field which is used to identify teams for Backlog level issue types and provide the unique value which identifies the team.
Team field mapping for Solution Train sessions
In the RTE cockpit, navigate to your ALM connection and in there to the ART mapping area. There you can find a separate Tab to do the team field mapping.
Select your team field which is used to identify teams for Backlog level issue types and provide the unique value which identifies the team.
Supported field types
The following types are supported to sync teams between Jira (Cloud and Data Center) and piplanning.io:
Custom field of type Single-Select
Labels field
Custom field of type Multi-Select
→ If multiple values are specified in the mapping, all need to exist on the work item in Jira for a match
Custom field of type Checkbox
→ If multiple values are specified in the mapping, all need to exist in Jira for a match
Jira Team field
→ To find a team's ID on Jira Cloud, see these instructions→ This is supported on Jira Cloud, and on Jira Data Center (in v2.19.0 or higher)
Please reach out to us if you need other field types.
New (October 2024)
You no longer have to use field-specific formatting when entering the values. Instead, just enter the value(s), separating multiple values with commas.
IMPORTANT
Please check twice that the all values entered in the Team field mapping configuration, that they actually do match the values in Jira, when adding the field value/s into piplanning.io because hidden whitespaces or incorrect spelling in Jira values or piplanning.io values can cause mismatches.