Skip to main content

How to configure Jira and PI plan in Advanced Roadmaps

Learn about the Jira configuration changes needed to support the recommended PI plan configuration use cases and how to configure a PI plan to coordinate cross-team planning in Jira Premium.


Before members of the product management team and the agile teams can use the PI plan, a Jira admin, and a PI plan admin will need to configure the system to support the use cases described in How to schedule work in the Shared PI Plan with Advanced Roadmaps. A PI plan admin is responsible for configuring a reusable plan for both pre-PI planning and the PI planning event by all the teams in the program.
This plan configuration is designed to be reused for future PIs with modifications to the views, configuration, and issue sources as needed over time. Be sure to make necessary adjustments if the current configuration of your projects and team boards requires it. Typically, the RTE or program manager is the PI plan admin.


You will need a Jira admin to complete the below Jira configuration steps. Please note, some of these items may have already been implemented from other solution guide pages. Think of this as a full inventory of all the system configurations and disregard steps to create custom fields or projects that already exist.

In Jira:
  1. Verify all the end-users are able to access the plan tab in Jira: Types of permissions in Advanced Roadmaps.
  2. Create WSJF fields and WSJF calculation.
    1. Note: Creating the WSJF field is referenced in How to assign WSJF to work items.
  3. Create a custom field called business request date using the date type field.
    Field name bus req 1
  4. Confirm the PI custom field is present on Jira epics.
    1. Note: Creating the PI custom field is referenced in How to configure program increment (PI) objective projects and boards.
      Create issue pic2
  5. Create a new multi-select custom field called contributing teams with your organization teams as options.
    1. Add this field to the Jira epic issue type you'll use for planning with Advance Roadmaps.
      Contributing team pic3
      Roadmap Pic4
  6. Create a new single-select custom field called t-shirt size for Jira epic.
    T shirt pic 5
  7. Create a new company-managed project for program features. This project will only include Jira epic issue types.
    1. Include all the following fields in the screenshot for create, edit, and view screens for Jira epics.
      Field tab pic6
      Field tab WSJF pic7
      Create a paragraph custom field called value statement and include the value statement prompts as the default value. See the example value statement in the screenshot.
  8. Add the field to the Jira epics issue type
    Create issue value Pic8
  9. Create a new company-managed objective project using the kanban template and objective issue type.
  10. Note: Creating the objective project and issue type is referenced in How to configure PI objective projects and boards.
  11. Create a new company-managed project for initiatives using the kanban template. This project will only include initiative issue types.
    1. Create initiative issue type. Include all fields for create, edit, and view screens.
    2. Update the organization hierarchy.
Note: Interjecting between existing levels will break existing parent links.
Field tab pic9

The following steps are for the PI plan admin to configure.

Note: PI plan admin in this document refers to the person or people who will be editing and configuring the plan and will require Advanced Roadmaps user permissions.

In Confluence:
  1. Navigate to the PI planning prep page or the program team pageand reference the projects and boards the team currently works in.
  2. Identify feature issue sources that may appear outside of the team boards.
In Jira:
  1. Select plans, select create plan.
    1. In create plan: Give the plan a name that clearly identifies the program and PI plan. For example, “Waze Pprogram PI plans.”
    2. For access, select open.
    3. For issue sources, include all the issue sources that will be needed to target Jira epics to the upcoming PI.

      Note: We strongly recommend you create all Jira epics in their own single project for process visibility and approval. This is a great way to manage works in progress (WIP) and enable accurate reporting. However, if a single epic program project is not an option, then each team should create and manage its own epics in their projects. You can then create a kanban board with all of the program Epics you'll use as an issue source.

  2. Refine issues displayed, and set exclusion rules as needed.
    1. Select create
      Create plan pic 10
      exclusion rule pic 11

      Note: In your newly created plan, review the data results presented and begin to modify configurations.

  3. Select plan settings.
  4. Select scheduling and choose the appropriate estimation option.
  5. For dates, select target start and target end.
  6. For inferred dates, select the appropriate option.
  7. For dependencies, select concurrent. We recommend concurrent, especially for Jira epics, so start and end dates can overlap.
  8. Saved views will be covered below in the create and save views section.
  9. Select issue sources and make any modifications as needed. We recommend using boards over filters if possible to reduce the need for filter maintenance.
  10. Select exclusion rules and other source data options as needed. We recommend setting exclude any completed issues after* to 90 days.
  11. Select removed issues and make any additions as needed.
  12. Select custom fields.
    1. Select add custom field and include all unsupported or custom fields relevant to epic value assignment, estimation, and prioritization. We recommend including the following fields:
      title desc pic 12
    2. Add additional fields as needed.
    3. Exit plan configuration and select back to plan.
In Advanced Roadmaps
  1. Select teams.
  2. Select add teams to your plan.
  3. In managed shared teams:
    1. Create a shared team for each of the teams in the program shared teams.
    2. Within your PI plan, select teams
    3. Select add existing team
    4. Add the required shared teams for the program
      add a team to yur plan pic13
  4. Go back into each team's setting, make adjustments as needed, and confirm each team is associated with their team issue source.
    Shared team pic new 14
  5. Create cross-project releases to include all the epics and stories that will be delivered across teams. If the program shares a common project for all issues, you can skip this step.
    1. Select releases.
    2. Select create cross-project release.
      1. Cross-project releases group Jira fixed versions into a collection of versions that can be named something familiar to your organization, such as milestones:
        Cross project pic 15
Example of a cross-project release based on milestones:
cross project release pic 16

Note: Cross-project releases are only used in Advanced Roadmaps and can't be saved to your issues in Jira.

c. Select create.
  1. In this step, you will create standardized views to support different planning needs.
    1. Select timeline.
      1. High-level planning view.
        1. Create a new view and name it “High-hevel planning,” or a name appropriate for your organization.
        2. Select filters, for the hierarchy, select initiative to story.
        3. Select fields.
        4. Choose all the appropriate fields to display:
          High level planning view pic 17
        5. Select save.
      2. WSJF view:
      3. Target Epics to PI - PI plan view
        1. Create a new view and name it “WSJF,” or a name appropriate for your organization.
        2. Select fields.
          1. Choose all the appropriate fields to display such as: status, PI business request contributing teams, t-shirt size:
            Target epic to PI Pic 18
          2. Select view settings, sort by rank, group by PI:
            View setting by Rank pic 19
          3. Select save.
      4. PI status reporting for leadership view.
        1. Create a new view and name it "PI status reporting for leadership,” or a name appropriate for your organization.
        2. Select filters, for the hierarchy, select initiative to story.
        3. Select fields
          1. Choose all the appropriate fields to display:
            PI status reporting for leadership pic 20
          2. Select save.
To share your saved views:
1. Select share as, in the upper right of plan.
2. Copy the link to share the roadmap.

Note: You can share plans in Confluence with the Advanced Roadmaps for Jira macro.

Recommendations on items to maintain in the PI plan:
  • Issue sources
  • Exclusion rules
  • Releases
  • Teams
  • Saved views


  • Roadmap view of the PI plan


Was this content helpful?

Connect, share, or get additional help

Atlassian Community