Working with scaled boards

Scaled boards visualize the work planned and performed across multiple Jira Scrum boards in order to provide you an overview of a large-scale project that is being developed in multiple Jira projects. You can also change the views of the board depending on individual needs and manage the issues.

Accessing a board

Scaled boards can be accessed from:

  • Boards list in Scaled boards → Manage Scaled Boards clicking on the name of the board


  • Favourite boards from the Scaled boards menu if any boards have been marked as favourite

Using board view

The board view displays all sprints from the Jira Scrum boards selected for the teams added to the scaled board.

The number of sprints displayed on a scaled board by default can be set in the configuration.

Sprints on a scaled board are described with Sprint Name and Goal as the header. Issues assigned to the sprint are displayed with the following information:

  • Status category

  • Issue type

  • Issue key

  • Summary

Issues that were not completed and have a negative resolution set will be crossed out. This state may indicate that the issue was e.g. rejected, canceled, closed as a duplicate.

The resolutions that will be treated as negative can be set in the configuration. If the default configuration is applied to the board, the negative resolutions are Won’t Do, Rejected, Canceled.


Issues can be moved between sprints of the same team (the same Jira board) using drag and drop. Only sprints that were not closed can have their scope changed. Issues moved to a different sprint will have that sprint changed in Jira. All the events applicable to such a change (e.g. a notification sending) will be triggered as if the sprint was changed in Jira directly.

Using the top bar

The top bar contains various actions that customize the view of the board.

  1. Scope change panel allows you to change the visible on the board scope by moving to past or future sprints using arrows. You can also zoom the view in or out to see fewer or more sprints respectively.

  2. Pre and post planning view shows the pre planning and post planning columns with issues according to the filters set in the configuration for each team.

  3. Card view displays issues as cards with additional data.

  4. Dependencies view displays the links between issues that are configured as dependencies for the scaled board. For the dependency to be visible, both linked issues have to be visible on the scaled board.

  5. Epic view/Issue view hides the issues in sprints and shows the epics to which these issues belong.

  6. Overview hides all issues on the board to show only the sprint name and goal to display the overview without details.

  7. Board configuration opens the setup of the board. The action is only visible to the users granted the administration permission to the scaled board