-
Bug
-
Resolution: Fixed
-
Low
-
None
-
8
-
Severity 3 - Minor
-
1
-
Issue Summary
Manage Sprints permission will not work as they should for projects that have a complex filter for users that aren't Jira-administrator if one of the projects is archived.
How to know if the filter is complex?
You'll see the following message on your Board Setting page:
We can't show the projects on this board, because the board's filter doesn't specify any. Your users may have trouble managing issues and sprints on this board. Try including some projects in the filter to fix this.
Steps to Reproduce
- Have a user/group set with the Manage Sprints permission for all projects
- Have a Scrum project using a complex filter on its board
- Ensure that the user is capable of Managing Sprints and that the user is not part of the groups that allow the Global Administer Jira permission
- Archive a random project
- Check again and see that the user is not capable of managing sprints anymore
Expected Results
The user should be able to manage sprints on a project that has a complex filter.
Actual Results
The user is unable to manage sprints on the project that has a complex filter. They would receive the following message:
Workaround
Right now, the only known workaround is to restore the archived project, delete it (moving to trash should also work) or change the filter specifying the projects that you need.
- is related to
-
JRACLOUD-79783 Sprint permissions do not work with a board complex filter and a private team managed project
-
- Closed
-
- relates to
-
JRACLOUD-81454 Manage Sprint permission breaks on project with a complex filter if any project is archived
-
- Gathering Impact
-
-
C2CJ-563 Loading...