How to restrict access to the sprint for the same project but from the different board?
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
To ensure proper project management, we have two sprints: SprintA and SprintB. For our team's needs, we require read-only access to SprintB, while full access is necessary for SprintA sprint. Both the sprints are derived from two different boards - BoardA and BoardB respectively.
Environment
9.4.3
Solution
We are assuming there are two boards BoardA and BoardB. The sprint will be created from the respective boards.
Kindly attempt the subsequent steps and evaluate if they have assisted you in fulfilling your needs.:
- First, you need to create two groups of users: one group for users with read-only access to the BoardB board and another group for users with full access to the BoardA board.
- Go to Jira Administration (cogwheel icon) > User Management > Groups. Create the two groups, e.g., "sprintB-read-only" and "sprintA-full-access"
- Add the appropriate users to their respective groups.
- Now, you need to create a custom permission scheme for the project. Go to Jira Administration > Issues > Permission Schemes. Click "Add Permission Scheme" and name it, e.g., "Custom Project Permission Scheme."
- Edit the newly created permission scheme by clicking on the "Permissions" link in the Actions column.
- For each permission, you need to customize the access by clicking on the "Edit" link. For example, for the "Browse Projects" permission, remove the default access (like 'Project Role: Users') and add the two groups you created earlier.
- For the permissions, you want to limit to read-only access for the BoardB board, remove any write/edit access for the "sprintB-read-only" group. For example, remove this group from permissions like "Create Issues," "Edit Issues," "Transition Issues," etc. Make sure to keep the "View Issues" permission for this group to maintain read-only access.
- For the BoardA board, ensure that the "sprintA-full-access" group has all necessary permissions, such as "Create Issues," "Edit Issues," "Transition Issues," etc.
- Now, you need to associate the custom permission scheme you created with the project. Go to Jira Administration > Projects, and find your project in the list. Click on the project name to open its settings.
- In the project settings sidebar, click on "Permissions." Click on the "Actions" button (three dots) in the top right corner and select "Use a different scheme." Choose the "Custom Project Permission Scheme" you created earlier and click "Associate."
- Finally, you need to set up the board filters for both the BoardA and BoardB boards to ensure they only show issues relevant to each board. Go to the respective board > Board settings (three dots) > General. Edit the "Saved filter" to include a filter query that separates issues for
BoardA and BoardB, for example by using a custom field, label, or component. - Make sure to share the filters with the respective groups ("sprintB-read-only" and "sprintA-full-access") to avoid access issues. Go to Issues > Manage Filters, find the filters you used for the boards, click on the "..." (more options) button, and select "Edit permissions." Add the respective groups in the "Group" field under "Shares."
Now, users in the "sprintB-read-only" group should have read-only access to the BoardB board, while users in the "sprintA-full-access" group should have full access to the BoardA board. Create sprint from the respective board and test.