nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sprint Manager not able to Move up or Move down Sprints

Durga Magesh

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?

Accepted answers

Durga Magesh

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

All comments

Bill Sheboy

Hi @Durga Magesh

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/

Kind regards,
Bill

Durga Magesh

Hi Bill,

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?

Thanks,

Durga

Bill Sheboy

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!

Durga Magesh

Here is the screenshot. Pls let me know if this helps.

Filter Query: project = OWB ORDER BY Rank ASC

Screen Shot 2022-05-24 at 12.23.36 PM.png

Durga Magesh

The issue is resolved.

Thanks, @Bill Sheboy

Bill Sheboy

Thanks, and I am glad to learn it is resolved. Definitely a curious set of circumstances for this one.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud