Creating scaled boards

New scaled boards can be created in Scaled Boards → Create Scaled Board.

Basic setup

When creating a new scaled board using the basic setup, you will need to provide the minimum information required. The default configuration will be applied to the board and it can be changed after the board is created.

  1. Enter the Board name. Make it meaningful. It could include the name of the project or product the board will be used to manage.

  2. Optionally enter the Board description to explain the role of the board in more detail.

  3. Add a new team. Provide the Team name to identify the group that is working on a specific project (or a part of it). Select the Board to indicate the Scrum board the team is working on. Click the plus icon.

  4. Add more teams to include all teams that will be working on the project.

  5. Click Create board to create your scaled board.

The first team added is considered to be the core team and its Scrum board will be the reference one for the scaled board in terms of start/end sprint dates. In order for the scaled board to work correctly, the Scrum board of the first team needs to have active sprints.

Only Scrum boards are available for selection when adding a team to the board.

Advanced setup

If you don’t want to use the default configuration for your board, you can click the Advanced setup link to go through the board configuration wizard.


The step is the same as the basic setup. Please refer to the section Basic setup above on this page.


Configure the view of the board. Decide how sprints will be displayed and define resolutions considered as negative for issues.

Default view

  1. Set the Select reference sprint type to decide if the reference sprint should be the active or specific one. If the Selected was set, select the sprint in Select sprint. The sprint selected here will be focused by default when viewing the board.

  2. Choose how many past (completed) sprints will be displayed on the scaled board in the Number of past sprints to display.

  3. Choose how many future sprints will be displayed on the scaled board in the Number of future sprints to display.

  4. Set the duration of the sprint in Sprint duration in weeks.

Negative resolutions

  1. Decide if issues with specific resolutions will be marked (crossed out) on the board’s view in the Enable negative resolutions. If the negative resolutions are enabled you can set Resolutions.

By default the Won’t Do, Rejected will be set in the Resolutions if found in Jira.


Visualize the relationships between different issues based on the issue links in Jira.

  1. Select the Link type that will be visualized on the board.

  2. Select the Color in which the link will be displayed.

  3. Click Add.

Card Layout

Cards are a form of displaying issues on the board. You can configure the layout of cards to display different data from fields on the issue.

  1. Add row to be able to configure fields and add cells.

  2. Click the plus icon to divide the row into cells.

  3. Select the fields in each cell to display it on the card/issue on the board.

You can have two rows and four cells in each row on your card layout.

Fields that can be set in the card layout are the Jira built-in custom field types and system fields. Non-standard fields introduced by other apps are not supported.


Set the filters for planning columns used for displaying issues before and after planning work on the board.

  1. Enable modules to configure the columns.

  2. Enter PRE issues JQL and POST issues JQL to set the filters that will display the issues in respective columns.

  3. Define the filters for each team added to the board.


You can grant permissions to the users of your board to separate the duties according to the roles. Following permission types can be set:

  • Access - permission to view the board, zoom in and out, move between future and past sprints, filter the view

  • Work - permissions to move issues between sprints

  • Administration - permissions to configure the board

  1. Each permission can be granted to Everyone, Only owner or Selected groups.

  2. If you decided to grant the permission based on Jira user groups, such groups need to be set in the Group field.

Global permissions defining the access to the JSAB app are superior to the board permissions i.e. if a user has access to the board, but doesn’t have access to the JSAB app, he will not be able to see the board.

The owner is the user that created the board.