| Table of Contents |
|---|
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.
...
| Include Page | ||||
|---|---|---|---|---|
|
Topics
| Table of Contents | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
There are two ways to get to Plan Settings. If you are in the plan click “Settings“ gear close to plan name.
...
If you are at Manage Plans page select “Settings” from the action menu for appropriate plan.
...
| Info |
|---|
You can only access Settings screen if you are listed as one of Plan’s Administrators. Read more on Permission Management below |
General settings
Probably the very basic thing you can do on General section of the settings is to change the name or your plan. We use in line editing, so just click on it to alter.
Projects on the plan
In addition to name change you can also amend a list of Jira projects you associate with your board: - the ones you picked up during board creation.
...
| Info |
|---|
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 plan that have already been added to the board plan by other users. |
Once you delete project from the list all the releases (versions) from this project will be deleted from the plan. And logically, once you add new project to the list all the releases (versions) from this project will be added to the plan.
Permissions management
There are two levels of board plan permissions, namely Administration and Browse permissions.
...
Administration permissions
Board Plan Administrators are able to browse the board plan and change its configuration. It is possible to add few couple of Administrators to the board plan by mixing individual users and groups.
| Tip |
|---|
Global Jira Administrators have administrative access to each |
...
plan. It doesn't matter if they are explicitly added to the |
...
plan as Administrators, or not. |
| Note |
|---|
The |
...
Plan 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. |
...
...
Browse permissions
Browse board plan permissions are granted by using the "Share board plan with" feature. Board
| Tip |
|---|
Plan Administrators and global Jira Administrators have |
...
plan browse permissions by default. |
If the user has Browse board plan permission but does not have Browse Project permission - releases (versions) from those projects will not be shown on the boardplan. In that case, the user will see a warning next to the board name:
...
There are 3 options to share the boardplan:
...
Users of projects in board plan
this option grants View Board Plan permission to all users who have permission to view projects added to the boardplan.
Users of specific projects
View Board Plan permission is granted to all users who have permissions to browse selected projects.
Users and groups
share Share the board plan with specified users and groups by granting them View Board permissionPlan permissions.
Hide outdated
...
items on Roadmap and Calendar
You can automatically hide releases items on Roadmap and Calendar that have not been update for sometime. The following time intervals are supported:
...
...
Color coding for
...
items on Roadmap and Calendar
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 VersionRelease)
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
...
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
...
Blue - Unreleased
...
Sprint StatusState
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
...
Grey - Todo
...
Yellow - In Progress
...
JQL Version
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 above 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 any of the item on Roadmap or Calendar view to show details popup. Close to the name you will see a pallet with an option to pick up a custom color.
...
Manage package workflow
On the Package workflow screen the Board Administrator can:
Customize a package flow by adding or removing columns on the board.
Rename columns.
...
A new column is added at the bottom of the columns list.
Manage columns
It is possible to perform the following action with columns:
Update column name.
Delete column.
Change column order.
Change name, status or delete a column
Column name may be changed by using in-place editing within the table. These changes will be saved automatically after finishing the update.
The column will be deleted by click on "Delete" button.
If a column contains at least one package it will not be possible to delete it. In order to delete the column, you will need to move all packages from the column before taking this action.
Manage transitions
Restrictions
You can restrict transition from one column to another by specifying two additional checks, namely:
...
Permissions. Outline only specific users and/or groups that are allowed to make the move.
E.g. only Compliance team can move packages from “Ready for Compliance Review“ to “Ready for Delivery“.
JQL based. Define a custom JQL that will be executed upon issues comprising the package and specify conditional clause from transition.
E.g. all Epics should be “Ready for Development“ before package moves to “Ready for Development“. Or there should be Zero bugs before package moves to “UAT“.
...
Auto-generation of Release Notes
You can also trigger automatic release notes generation for package upon move to specific column
To do so click “Manage“ for the column and turn on “Trigger Release Notes generation“. You would need to pick up one of the Release Notes templates for packages.
...
Package and Versions workflows sync
If you want to move all corresponding packages into specific column upon package move you can select this option in “Manage“ popup.
...
Versions workflow section
On the Versions workflow screen, the Administrator of the Board can:
Create/update/delete version workflow statuses (aka columns).
Change the mapping between columns and standard Jira version statuses.
...
A new column is added at the bottom of the columns list.
Manage columns
Columns represent statuses of release version workflow. The following actions are allowed upon Board Administrator permissions:
Update column (status) caption.
Update mapping to Jira standard status - Released/Unreleased.
Delete column.
Change column order (sequence of steps in the release process).
Change name, status or delete a column
Column name or mapping to Jira standard status could be changed using in-place editing in the table. The changes will be automatically saved after completing the update.
...
The column will be deleted by clicking on the "Delete" button.
Limitations
In cases where the column contains at least one version, it will not be possible to change the column status or delete it. In order to delete or change the column, please move all versions from the column before implementing this action (Deletion).
It is not possible to change the column status or delete default columns, marked by icons: “blue” and “green” I-icons
Reorder columns
Re-ordering of Columns can be done using drag-and-drop.
...
Columns are equivalent of steps in your Release Management process, so by changing the order of the columns you automatically changes the sequence of the process steps.
Manage restrictions
You can restrict transition from one column to another by specifying two additional checks, namely:
...
Permissions. Outline only specific users and/or groups that are allowed to make the move.
E.g. only Compliance team can move version from “Ready for Compliance Review“ to “Ready for Delivery“.
JQL based. Define a custom JQL that will be executed upon issues comprising the version and specify conditional clause from transition.
E.g. all Epics should be “Ready for Development“ before version moves to “Ready for Development“. Or there should be Zero bugs before version moves to “UAT“.
...
Webhooks
🆕 Blackout Periods (Non-working Days) [from Feb’22]
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.
...
Blackout Periods (Non-working Days)
Check out respective section of documentation for Blackout periods (or Non-working days) feature.
| Include Page | ||||
|---|---|---|---|---|
|