"Complete sprint" button is missing for certain users

[Leon Gumba]

Hey everyone!

We have a new Scrum project where I recently moved over 1000 issues from another Scrum project, many of which came with their sprints. Now, I see three different active sprints in this project.

As a Jira admin, I have the "Complete sprint" button available in both Active sprints view and Backlog view, but other users who work on this project (and who are not Jira admins) can't see these buttons in either of those views. They do have the "Manage Sprints" permission, I've double-checked it already.

What could be the issue here? We didn't have the "Parallel sprints" setting enabled, so I've already tried enabling it, but it didn't help. I also asked the users to log out of their accounts and log back in, but that didn't resolve it either. The project filter only includes issues from this project, so that shouldn't be causing the problem.

At this point, I'm out of options and ideas. Why is this button missing for certain people but not for Jira admins? Can anyone please suggest possible solutions given what I've tried so far?

[Ramin Shanehsaz · Accepted solution]

Hi,

you have to ensure, that the users have the "Manage Sprints" permission for every project, from which issues are included in the sprints, you want to close.

So, I would double-check if the Scrum Board's filter maybe includes other project's issues, where you have "Manage Sprints" permissions, but the other users don't. This happens often by an "OR"-clause.

Best,
Ramin

[Leon Gumba]

Hi @Ramin Shanehsaz ,

Thanks for your reply!

The board's filter is alright. Here's the query:

project = PLAT ORDER BY Rank ASC

So only this PLAT project is targeted.

[Ramin Shanehsaz]

Then, maybe you have scenario 2 in the following Atlassian KB article: https://confluence.atlassian.com/jirakb/some-users-can-t-manage-a-sprint-create-start-edit-complete-move-due-to-incorrect-project-permissions-1125881102.html

I would go through the described steps to fix this problems with your Jira admin or, if you can close the sprints, you should do this to get a "clean cut" for the moved issues and from as of now the users can create new sprints in the board and also close them.

[Leon Gumba]

Thank you for this link. You were right. As a Jira admin, I had to complete those bugged-out sprints myself, and now other project members can manage sprints.

[Ramin Shanehsaz]

Nice to hear that it's working now :)

[Lisa Forstberg]

Hi @Leon Gumba ,

I would doublecheck the filter of the board again.

Users need to have the managed sprint permissions for all issues that can potentially be visible on the board, not only the ones currently visible on the board

If the board filter is too open, potentially matching issues from all projects in your whole instance the users need to have managed sprint permissions for all projects.

Can you show us the JQL for the board?

best regards

Lisa

[Leon Gumba]

Hi @Lisa Forstberg ,

Thanks a lot for your reply! Here's the filter query:

project = PLAT ORDER BY Rank ASC

Should be OK. The PLAT project is the project in question.

[Sanam Malleswari]

Hi @Leon Gumba 
Try Recreating the Sprints: Ask the users to create new sprints This could reset  underlying issues with migrated sprints.
Browser Cache: Users should try clearing their browser cache or using a different browser to rule out any local caching issues.
If the issue is in Jira server or datacenter application, then try to re-index the project.

Kind regards,
Mallika