Table of Contents | ||||
---|---|---|---|---|
|
In case you’re using a field to identify your Team on program level issue types (i.e. Features, Enablers, Epics), you can synchronize the team field with the sticky types visualized on the program backlog board.
We separate two cases
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 and the piplanning app:
Customfield of type single-select
{"value": "<team name / select value>"}Code Block Labels field
Customfield of type multi-select
→ If multiple values are specified in the mapping, all need to exist in Jira for a match
Customfield of type checkbox
→ If multiple values are specified in the mapping, all need to exist in Jira for a match
Team field
→ To find a team's ID, see these instructionsPlease reach out to us if you need other field types.
Info |
---|
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. |