In order to navigate to the Board’s Admin Page, click on the "Settings" button in the top right corner of the release board or select “Settings“ from the actions list on the “Release Boards“ Page.
The board configuration screen consists of few sections, namely:
General
allow users to configure basic board parameters, add and/or delete projects and (coming soon) share the board with other users.
Versions workflow
helps to define custom release versions workflow by adding, changing or removing columns. Also, defines a mapping between Jira "Released" / "Unreleased" standard statuses and custom columns on the board.
General section
On the General section an administrator can:
Available now:
change the board name
add or remove projects from the board
Coming soon:
add or delete board administrators
There is no need to confirm the changes. They are saved automatically once control losses the focus.
Projects on the board
You can add projects to the release board and/or remove them. All Versions from selected projects are displayed on the board.
Project picker outlines only the projects where current user has “Browse project” permissions. Otherwise, the project will not be available from the list. The same logic is applied to all other projects on the board that have already been added to the board by other users.
Permissions management
There are two levels of board permissions, namely Administration and Browse permissions.
Board Administration permissions
Board Administrators are able to browse the board and change its configuration. It is possible to add few Administrators to the board by mixing individual users and groups.
Global Jira Administrators have administrative access to each release board. It doesn't matter if they are explicitly added to the board as Administrators, or not.
The Board Administrators can delete themselves from the list unless there is at least one active Administrator remaining in the list. If user tries to delete the last remaining Administrator of the list the warning message will appear preventing this action to happen.
Board Browse permissions
Browse board permissions are granted by using the "Share board with" feature. Board Administrators and global Jira Administrators have board browse permissions by default.
If the user has Browse board permission but does not have Browse Project permission - versions from those projects will not be shown on the board. In that case, the user will see a warning next to the board name:
There are 3 options to share the board:
Users of projects in board
this option grants View Board permission to all users who have permission to view projects added to the board.
Users of projects
View Board permission is granted to all users who have permissions to browse selected projects.
Users and groups
share the board with specified users and groups by granting them View Board permission.
Hide outdated releases
You can automatically hide releases that have not been update for sometime. The following time intervals are supported:
🆕 Color coding for releases
You can configure color coding for cards on the board and bars on the Roadmap and Calendar. Most of options are based on release workflow state or release scope progress.
The rules are the following:
Version (Fix Version)
By Board Column Status (Default)
Blue - Unreleased
Green - Released
By Progress
Green >90% are Done
Yellow >20% are Done
Orange >5% are Done or “in progress” !=0
Grey - 0% done
Custom (see below)
Grey by default
with option to select custom color coding for individual Fix Versions
Epic
Board Column Status (Default)
Blue - Unreleased
Green - Released
By Epic Status
Status Category (Todo, In Progress, Done )
By Progress
Green >90% are Done
Yellow >20% are Done
Orange >5% are Done or “in progress” !=0
Grey - 0% done
Custom (see below)
Grey by default
with option to select custom color coding for individual Epics
Sprint
Board Column Status (Default)
Blue - Unreleased
Green - Released
Sprint Status
Grey - Not Started
Blue - In Progress
Green - Done
By Progress
Green >90% are Done
Yellow >20% are Done
Orange >5% are Done or “in progress” !=0
Grey - 0% done
Custom (see below)
Grey by default
with option to select custom color coding for individual Epics
Virtual Version
Board Column Status (Default)
Blue - Unreleased
Green - Released
By Progress
Green >90% are Done
Yellow >20% are Done
Orange >5% are Done or “in progress” !=0
Grey - 0% done
Custom (see below)
Grey by default
with option to select custom color coding for individual Epics
Package
Board Column Status (Default)
Grey - Todo
Yellow - In Progress
Green - Done
By Progress
Green >90% are Done
Yellow >20% are Done
Orange >5% are Done or “in progress” !=0
Grey - 0% done
Custom (see below)
Grey by default
with option to select custom color coding for individual Epics
Custom color coding
If you select Custom in any of the dropdowns all the release items of selected category (Fix Versions, Epics, Sprints, JQL versions) will be color by default in Grey. But this turns on the flexibility of coloring individual release items with the pallet you like (similar to Epics in Jira).
To do so click on release item to show details popup. Close to the name you will see a pallet with an option to pick up a custom color.
Blackout Periods (Non-working Days)
Configurations
In “Non-working Days“ section of Board Configuration you can setup backout periods.
To create one put the name you would like to use in the hints, start/end date and one of suggested colors from the pallet. The periods could not be overlapping.
We support inline editing so to amend click on any property of existing period in the grid to change.
To delete period click on delete button on the right. You would need to confirm before blackout period will be permanently deleted.
Roadmap and Calendar views
Once configured in board sessions backout periods will be shown on Calendar and Roadmap view using the shades of the colors picked up. Once you put the mouse on the day caption a tooltip with backout hint will be show.
Same functionality is available in Roadmap and Calendar gadgets.
