Hi Folks,
We hope this message finds you.
We are releasing Permissions Management for our Advanced Kanban & Agile Board for Jira. From now on you will have 3 tiers of permissions, namely:
Board Administrators to have full control of the board and the only user/group that have access to board settings and can alter it besides Jira Global Administrators obviously
“Work with the board” to add, remove or change configuration of columns/swimlanes w/o ability to change what are the standard or custom fields are defined for columns/swimlanes, create/update column groups, create links/dependencies, setup WIP and Aging limits, create or change quick filters and most important drag and drop issues
“Read only access” to view the board only and only apply quick filters or other filters, turn on/off statistics, view dependencies, collapse/expand columns/swimlanes, zoom in and out.
While migrating we will
assign the creator of the board as Board Administrator. Jira Global Administrators are also Board Administrators by definition. So, if you can’t access the board please contact the creator or Jira Global Administrator to give you appropriate permissions.
users/groups that can manage projects shortlisted for the board will receive “Work with the board” permission. It’s recommended for Administrator to go over automatically assigned permissions to verify and maybe distinguish between “Work with the board” / “Read only access” permissions
no one will receive “Read only access” automatically and needs to be set manually by Administrators
As always, please reach out to our support team for any questions and support you during transition.
Many thanks & Kind regards,
Support Team by Release Management Apps
Introduction
There are two levels of permissions for Advanced Kanban and Agile Boards, namely:
Global Permissions to access the App from the Apps menu as well as project left navigation panel
Board level permissions to distinguish who can access different functionality of the App
All permissions could be set for Users and/or Groups.
Global permissions
Global permissions are created automatically when installing the App. There is ongoing issue with Atlassian when on some sporadic cases Global permissions are not properly populated. In this cases, no one can access the App and Jira Global Administrators need to configure it manually.
If you do not see the App in Apps menu please contact your Jira Global Administrators to configure Global permissions manually to add you or/and group you are part of to the settings.
Board level permissions
At board level permissions are segregated between
Administrators, who can do everything, but the only role that can have access and change Board Settings, cluding adding/removing Administrators.
“Work with the board“, who can do everything but change board settings. This also presumes that Column/Swimlanes mapping is fixed and can't be changed by this role.
“Read only access” who can only view the board and (if selected) move issues on the board.
For the later 2 configuration is identical, namely you can define it for
Projects of the board, so users who has access to board selected projects will have appropriate role for the board
Other projects, so users who has access to other selected projects will have appropriate role for the board
Users/Groups, so only selected users/groups will be shortlisted to have appropriate role for the board
User needs to be at least in one of those configurations to receive appropriate roles for the board or to be a member of the Group that is part of above configurations
Board Administrators
Administrators are usually Board Creators, but can also be changed anytime. There should be at least one Administrator of the board so the App won't allow to delete all of them.
If you Board Administrator is not available and you need to make changes to board settings … no worries, Jira Global Administrators are Board Administrator by definition.
“Work with the board”
This is the main permission to operate the board.
Users with work access ..
Can do | Cannot do |
|---|---|
|
|
“Read only access”
Read-only access could be done it two ways, namely:
View only, no changes
Ability to move issues and as a result amend corresponding issue standard or custom properties mapped to columns/swimlanes (appropriate project level permissions will be checked).
Apart from the above, users with read-only access
Can do | Cannot do |
|---|---|
|
If the board is configured to automatically add columns/swimlanes .. appropriate columns/swimlanes will be propagated automatically
|
What if I can’t access the board?
We suggest reaching out to creator of the board (Board Administrator) or Jira Global Administrators to assign you appropriate permission for the board.