Skip to main content

Solution Train ART Backlog Board Sync [Jira]

This article is relevant for PI Sessions that are set up to support Solution Trains (multiple ARTs).

Updated this week

This article is relevant in case:

  • Multiple ARTs; a Solution Train is added on step #2 Teams

  • The PI Session is being prepared for a Solution train with two or more ARTs

Make sure that you first complete the ART Mapping. For a Solution Train session you must configure the mapping between Jira projects and ARTs in piplanning.io in your ALM Connection configuration.

ART Backlog Board Sync [Jira]

You can add one or more Sticky Types (optionally mapped to a Jira issue type) to the backlog board. As the Jira projects are already define in the ART-Mapping, you only need to specify the Issue Type, optional WSJF field, and any fields you want to use to distinguish issues in.

Number

Description

1

The name of the Sticky Type

2

The Jira Issue Type which is mapped to this Sticky Type. You will get a warning if the selected Issue Type is not available in all the projects defined in ART Mapping. You can continue with the warning - but the app will not be able to sync new stickies to this project in Jira.

3

This is optional. Specify the Jira field which represents the WSJF value / ranking of the stickies on the ART Backlog Board. The field will be ignored if this field is not available for all the issues in all the projects defined under ART Mapping.

4

Use these fields to identify this PI’s backlog issues in Jira. You may, for example, use a label such as PI1 or specify a FixVersion. Multiple values can be entered, separated by commas.

NOTE: If no Jira Fields are specified, all issues in your Jira project (that match the selected type) will be pulled into the PI.

Filter by Jira Fields

How to: filter the ART Backlog Board so only the top 10 or relevant Features are synchronized in this PI Session.

You may not want to have all the Jira issues of a project on the ART Backlog Board. In that case, you can choose (filter) to only sync issues that have a specific value for a given field.

For example, you can filter the Jira Issues/ART Backlog Board sticky notes based on fields in Jira such as the Label (eg. “PI6”) AND/OR Fix Version (eg. “1.12”).

The following Jira Field Types may be used to filter session ART Backlog Board (sticky note) items:

  • Labels

  • Versions

  • Components

  • Single-select (customfield)

  • Multi-select (customfield)

In the example above, only Jira Issues with the Label "PI24.1" AND Fix Version “24.4” will be synchronized on the ART Backlog Board.


Above is an example only, of the Jira Fields available on a Jira Project that can be used to filter the ART Backlog Board for the specific PI Session.

If you specify multiple Jira Fields, OR multiple Value(s) - separated by commas, then the fields/values will be added together using a query that has an AND statement. For example, using the Labels PI6, PI7 will only display Jira Epics/Issues which have the Labels PI6 AND PI7 set in Jira.

Keep in mind

Jira Labels do NOT have whitespace characters. Labels containing "/" cannot be used in the Jira Labels field as a filter.

Ranking

The sticky notes on the ART Backlog Board are ranked by the value on the bottom right of the Sticky from top left to bottom right.

You can rank them by any numeric field, which is available on the Jira Issue Screen of your synced Issue Type.

Team field synchronization

Sync the team field

You may want to make sure that a Features is pulled on the ART Backlog Board with a predefined team in case you already assigned a Team to that Feature before PI Planning.

To do so, please refer to the Jira Backlog Board - Team Field Sync article

Did this answer your question?