User with Project with Project Roles - Administrator, Project Editor, and Sprint Manager is able to Create and Delete Sprints. But when he tries to move up or move down sprint, he sees an error message - "Only a Jira administrator can update this sprint. Try selecting a project in your current board filter."
What additional permissions are required?
The issue is resolved.
One particular sprint in the current board (A) is associated with a sprint from another board (B) from another project (B). The other project (B) was archived and no longer in use. Atlassian support reviewed their database and shared the old Project, Board, and Sprint details. Once the sprint in the old project was deleted, the user was able to move the sprint up and down in the current project.
Thanks, @Bill Sheboy
For those sprints, is the board filter containing one or several projects? If there are multiple projects, I believe the person needs Manage Sprints permissions for all of the referenced projects. https://support.atlassian.com/jira-software-cloud/docs/how-do-jira-permissions-work/
Thanks for your response. I double-checked and the board contains issues of only one project.
The user belongs to a Jira Group which is mapped to the Permission scheme that the project uses. And the scheme has Create, Edit, Delete, and possible permission actions.
From the project settings, the User is mapped to Administrator, Project Editor, and Sprint Manager roles.
Are there any other checks that I can verify?
Let's stick with the board filter to diagnose this: if the filter is ambiguous it could still be trying to access multiple projects, as described here: https://support.atlassian.com/jira-cloud-administration/docs/use-manage-sprints-permission-for-advanced-cases/
Would you please post your board's filter? That will help to confirm if there are JQL issues. Thanks!
That filter looks good to me, so I am out of suggestions.
At this point, you could wait a bit to see if others post suggestions and/or submit a ticket to Atlassian Support to see what they say. They can see logs we cannot access and so may notice something causing this.
I just noticed something. In the same board, if I create sprints with no issues, then I am able to the empty sprints move up and down. But If I have to move the empty sprint above a sprint that contains issues, then I see the error message "Only a Jira administrator can update this sprint. Try selecting a project in your current board filter."
The only other thing I could think of was related to changing Rank (which is a different permission). But when I tested this scenario you describe...re-ordering sprints does not alter the rank, so that is not the cause.
As you can re-order empty sprints the cause is apparently related to the issues and not the sprints. Try manually re-ordering one issue to see what happens (with drag-and-drop); even though it worked for me you may get an error.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event