Jira Team Mapping

Setup team mapping (Jira projects to piplanning app teams)

Before creating a new jira-synced piplanning session, you need to tell the app from where it should pull the issues for each team. You can do that in the ALM team mapping in the cockpit.

  1. Navigate to "ALM Connections"→Select your Jira connection and edit → Team Mapping 
  2. Click on the "Edit" button of a team
  3. On the team-mapping screen you can set one or more Jira projects. 
  4. After selecting Project and Board you can click save.
    1. => The Project determines the Jira Project to which the stickies of that team are synchronized
    2. => The Board determines the Jira Board on which the sprints are created / existing of that teams

It will only show Jira boards of the type "Scrum". Kanban boards are not displayed as they can not be used for teamboards at the moment. We rely on sprints (to be mapped to iterations), and therefore need a Scrum-Board.


Q: Permissions: When I map a project and board to a team, I get the error "Give your Jira user the permission to "Create sprint" in this project". How can I fix that?
A: Make sure that the user you have used to connect the app to Jira (if you have used oAuth, the one which authenticated against Jira) has the "Create sprint" permission in that project. Keep in mind that you can be a admin of a Jira project and at the same time do not have the permission to create a sprint in that project. Also make sure that you selected a Scrum and not Kanban board.

Q: Missing Project: I can not find my project in the list of Jira projects.
A: Please make sure that the user you have setup the Jira connection has the permissions in Jira to read / list that project. Keep in mind that we only list 'classic' Jira projects (we do not support next-gen).

Q: Missing Board: I can not find the board when I want to map a team under the team-mapping page in the cockpit.
A: Please make sure that the board really belongs (is a child of) to the selected Jira Project. A board can be displayed in Jira in multiple projects, however it always originates from one single Jira project. You can see that in Jira if you go to the settings page of that Board. Workaround: You can hit "Show all boards" under "Advanced Settings" on the team-mapping page in the cockpit.