This article only applies for PI Sessions that support a Solution Train (multiple ARTs) configuration.
If you want to identify your ART on ART level Issue Types (i.e. Features, Enablers, Epics), you can use the ART field mapping to synchronize the ART field with the sticky types visualized on the ART Backlog Board
Mapping an ART field is a MUST in case you are setting up a Solution Train session and all the ARTs are working in the same Jira Project
ART field mapping
In the RTE cockpit, navigate to your ALM connection and in there to the ART mapping area. Here, you can find a tab for the ART field mapping.
Select which field is used to identify ARTs for Backlog level Issue Types and provide the unique value which identifies the ART.
Values should be comma-separated and entered without any special formatting
Supported field types
The following types are supported to sync ARTs between Jira and piplanning.io:
Custom field of type Single-Select
Labels field
→ If multiple values are specified in the mapping, all need to exist in Jira for a matchCustom field of type Multi-select
→ If multiple values are specified in the mapping, all need to exist in Jira for a matchCustom field of type Checkbox
→ If multiple values are specified in the mapping, all need to exist in Jira for a matchJira Team field (both on Jira Cloud and for Jira Data Center)
→ If you are using both piplanning.io On-Premise and Jira Data Center, then support for the Jira Team field in Jira Data Center is available in v2.19.0 or later.
Please reach out to us if you need to have other field types supported.