piplanning.io Team Mapping to Jira Projects
With any ALM Connection, but specifically for Jira in regards to this Help Article, it's essential to configure how we map the Team Boards in piplanning.io will map to the corresponding Jira Projects/Boards that are used by the Team. This is all done in the RTE Cockpit > ALM Connections > Team Mapping tab. The following steps can be completed by any User with the piplanning.io Admin Role.
Navigate to RTE Cockpit > ALM Connections > Edit > Team Mapping tab
Find the Team, and click Edit
Click +Add Project
In the Jira project dropdown field click Select project. Scroll and select the right Jira Project that maps to this Teams backlog.
In the Jira board dropdown field, click Select board. Find and select the corresponding Jira Board that this is used for the Teams Jira Sprints.
Optional: If the Team uses multiple Jira Projects to manage their Backlog Items then you can add additional mappings using the +Add Project button.
Figure I: Configuring the piplanning.io Team to Jira Project and Jira Board mapping in ALM Connections > Team Mapping.
The Jira Project determines where to synchronise the stickies for that Team.
The Jira Scrum Board determines the Jira Sprints to schedule the stickies into.
Note: By default only Jira Scrum boards appear in the Jira board dropdown field.
piplanning.io needs to map to Jira Sprints for the scheduling of Sticky Notes (Work Items) into Iterations. This necessitates the need for Jira Scrum Boards because Sprints in Jira only exist on Jira Scrum Boards.
If you have Kanban Teams, that is no problem, after all not all teams involved in a PI Planning Event are Scrum teams. Please read the article on Kanban Teams, and how to use a shadow Scrum Board, to complete this set up for Kanban Teams.
Optional: Mapping a Team field on Jira Issues
A common scenario you may have is one were there are several piplanning.io Teams using a single shared Jira Project. In this scenario it is likely that you will need to map to a Team field to differentiate what Team owns what backlog item (User Story etc.) in this single Jira Project. We can accommodate this scenario using the Team field (optional) mapping on the Team Mapping tab.
What needs to be done now is configuration of the Team field (optional) field in the RTE Cockpit > ALM Connections > Team Mapping tab. Check the Show advance settings checkbox.
Expand the section below for additional details.
ALM Connections > Team Mapping > Team fields (optional)
ALM Connections > Team Mapping > Team fields (optional)
Identify the field in Jira used to identify the Team. We support the following Jira field data schema types:
Single-Select Custom Fields
Jira Team field NEW
Jira Labels field
Jira Component field
Click the Show advance settings checkbox
Enter in the correct JSON syntax for the appropriate field schema type. Examples provided below.
Figure II: Mapping a piplanning.io Team to a Jira Project that uses the NEW Jira Teams field to denote team assignment on work items (Jira Issues) that will originate or display on the piplanning.io Team Boards
Optional: Mapping Default Field Values (*Required fields)
If you have additional required* fields on a Jira Issue that must be mapped in order to make the integration work please complete the Default field values (optional) configuration. Expand the section below for additional details.
Default field values (optional)
Default field values (optional)
Intentionally left blank. To be updated.