User has been given project admin role across all projects where stories originate. Still no luck in him being able to close a sprint.
I had an issue like this. The user had permissions to all projects involved, which was just two projects with a total of 8 issues.
I found via the Test View > By Sprint feature the Sprint was appearing on two boards. The JQL for both boards checked out fine when looking at the issues in the Issue Navigator.
However, one of the boards filters caused the Projects In Board to state The projects in this board cannot be listed because of the complexity of the board filter.
Because the second board wasn't needed we deleted it and then the problem with completing the sprint went away.
I am confident we could of fixed the JQL on the second board so Jira could identify the boards contained, and then we could of completed the sprint as well.
Faced this problem today.
My user used for a board a complex filter which included Scriptrunner JQL functions and Portfolio hierarchies.
Resolved by adding an additional conditional to the JQL, which limited it to the projects I wanted, where my user had manage sprint rights.
So instead of the complex filter I used:
(Project = MyProject) AND (My complex filter JQL here)
Worked like a charm and fixed all "Manage Sprint" permissions.
I hoep this helps anybody
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs