Board configuration

The configuration of scaled boards allows to change the behavior of the board in certain aspects and is organized into separate sections.


  1. Board name - name of the scaled board

  2. Board description - detailed information about the scaled board



Teams list allows defining the teams that will be working on a project that the scale board is created for.

  1. Team name - name of the team

  2. Jira board - Scrum board related to the team

  3. Add team - add the team to the list

  4. Remove team - remove the team from the list

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.

Pre and Post Plannings

Pre planning and post planning columns display the issues according to the applied filter. These columns can be used e.g. to see the upcoming tasks to be planned and the ones that were postponed for some reason.

  1. Enable modules - activate the pre planning and post planning configuration

  2. Pre issues JQL - JQL query for filtering issues in the Pre Planning column

  3. Post issues JQL - JQL query for filtering issues in the Post Planning column

Default View

Default View

The default view settings define how the board will be displayed by default.

  1. Select reference sprint type - sprint which will be focused

  2. Number of past sprints to display - number of upcoming sprints that will be displayed

  3. Number of future sprints to display - number of completed sprints that will be displayed

  4. Sprint duration in weeks - number of weeks that the sprint lasts

Negative resolutions

Issues having the resolution set to the one marked as negative will be crossed out on the scaled board view. Such issues should be considered as not completed and abandoned in a way.

  1. Enable negative resolutions - activate the negative resolutions configuration

  2. Resolutions - resolutions that will be treated as negative


Define dependencies between issues that can be visualized on the scaled board.

  1. Link type - link type to be treated as the dependency

  2. Color - color in which the dependency will be displayed

  3. Add - add the dependency to the list

  4. Remove dependency - remove the dependency from the list

Card Layout

Issues can be displayed as cards on the board view and here the layout can be configured.

  1. Add row - add a new row to add cells and set fields

  2. Add cell - add another cell to the row

  3. Remove row - remove the row from the layout

  4. Field - field that will be presented on the card layout of the issue

  5. Remove cell - remove the cell from the layout

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.


Different levels of access to the scaled board can be granted to the users. Each permission can be granted to everyone, the owner or specific user groups.

  1. Grant access permission to - allows viewing the board without the possibility to move issues between sprints.

  2. Grant work permission to - allows moving issues between sprints

  3. Grant administration permission to - allows configuring the board

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.

Delete Board

Deleting the scaled board cannot be reverted.