Overview of Team Field Mapping for the #5 ART Backlog Board
Team field mapping in piplanning.io enables the synchronisation of the specific field in your Jira Project/s that denotes the Team ownership of the 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 the ART level boards (i.e. the program-level work items), which are typically Features or Enablers (synchronized to Jira Epics or Jira Issues).
Figure I: Illustrates the automatic mapping of the Sticky Note Team field on ART Backlog Items when using the Jira-ALM Connection.
The following Jira field types are supported:
NEW Jira Team field
Single-Select custom fields in Jira
Jira Labels field
Jira Components field
IMPORTANT
IF, you are working with a PI Session that supports a single ART the configuration for the Team Field Mapping related to the ART Backlog items is done in SAFe PIs > PI Session > #5 ART Backlog Board
IF, this is for a PI Session that supports a Solution Train configuration, THEN this configuration is done in the ALM Connections > ART Mapping tab.
Steps on How To configure Team Field Mapping
Click to learn more...
Single ART PI Sessions
Single ART PI Sessions
Edit the PI Session > navigate to the #5 ART Backlog Board tab
Select the dedicated tab Team field mapping
Select the specific field from the Team field (optional) dropdown, that is used to identify the Team that is assigned to a work item
Complete filling in the correct JSON syntax that matches the Jira field type (e.g. Single Select, Label, Multi-Select etc.), adding the unique value for the Team values that are in Jira Software.
See below for JSON syntax examples to guide you in completing this step.
Solution Train PI Sessions
Solution Train PI Sessions
Navigate to the ALM Connections > ART Mapping tab.
Edit the ART
Select the Team field mapping tab.
Select the specific field from the Team field (optional) dropdown, that is used to identify the Team that is assigned to a work item.
Complete filling in the correct JSON syntax that matches the Jira field type (e.g. Single Select, Label, Multi-Select etc.), adding the unique value for the Team values that are in Jira Software.
See below for JSON syntax examples to guide you in completing this step.
Example JSON syntax for the supported Jira Field Types
Example JSON syntax for the supported Jira Field Types
Jira Single-Select Custom Field:
{"value": "<team/select value>"}Jira Labels Field:
["<label>"]Jira Multi-Select Custom Field:
[{"value": "<value>"}]Jira Checkbox Custom Field:
[{"value": "<value>"}]Jira Team Field:
"31d4610a-10ec-4457-a437-1eac5c50adb2"
TIP
To find the exact value to enter into the JSON syntax try either of the following:
Copy the field value/s to insert into the JSON from the Jira Issue Export XML or REST API response.
Contact us via the Messenger to set up a session and we will happily guide you through the configuration.
IMPORTANT
Replace the syntax in italics between the double quotes " " only. All other syntax is necessary JSON formatting.
Please check twice that the all values entered match the values in Jira, when editing that field.
Please check again, that the values entered into the JSON syntax match the values available for that field in Jira. We are making this friendly reminder to avoid having to spend time troubleshooting any typo issues which cause a false-positive mismatch during validation.