Error message "You need the manage sprint permission for all projects in the origin board to manage this sprint"

User has been given project admin role across all projects where stories originate. Still no luck in him being able to close a sprint.

 

4 answers

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

 

happy weekend

It worked. Thanks!

0 votes

Project admin does not necessarily mean manage sprint permission - check the permission scheme and user's membership for that.

permission scheme for Manage Sprints set to "Any logged in user"

For every project that might be included in the board?

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.

Can you explain how to get to the Test View > By Sprint feature?  We have multiple team sprint boards that pull in issues from lots of different projects, and I am unable to get our scrum masters access to manage sprints even though every single permission scheme in use has the scrum master user group in both Project Admin and Manage Sprints permissions.  I have resorted to adding them to the jira-administrators group in the meantime, while I work with atlassian support to resolve this problem.  Atlassian support told me that because our boards use complex filters, Jira simply ignores the permissions and won't allow users to manage sprints (they said for performance reasons).

And here is what I really want to know: if the jira-administrator group can manage sprints, with no apparent degradation in performance, then WHY THE HELL can't they create a sprint-manager user group that gives everyone in that group the ability to manage sprints??  Obviously this has been an issue for quite a while; it's incredibly disturbing that it hasn't been resolved yet.

@Jennifer McVicker

From the Backlog of the Scrum Board in the upper right corner is a Test View drop down button. The drop down choices are By Sprint and By Issues.

Sorry, I just saw this response.  You must be on Cloud JIRA, right?  We're on Server JIRA, v 7.8, and that option doesn't appear for me.

@Jennifer McVicker we are also running Jira Server, 7.6.9

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Statuspage

Introducing Statuspage Getting Started guides! First up: What is Statuspage?

Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...

21 views 2 1
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you