Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Complete Sprint button inactive only on one project

alessioLepaya January 3, 2023

Hello everyone,

We use the same permission scheme across many projects. It works perfectly in all of them but one. In this specific project, people added to the project with the Manage Sprints permission cannot complete a Sprint. The button is greyed out, and they get the message you need the Manage Sprints permission to complete the sprint.

  • The Board query is simple and gathers issues only from one project. It only filters out subtasks, but even by including them, the button stays inactive.
  • Using the permission helper confirms they have the proper permission to manage sprints.
  • I tried to remove the user and add it back, but no luck.
  • I tried to change the permission scheme and add it back, but no luck.
  • I added the same user with the same role o another project with the same permission scheme, and it works.
  • The user has also the edit issues permission

 

What am I missing?

4 answers

1 accepted

2 votes
Answer accepted
alessioLepaya January 4, 2023

I completed the Sprint as an admin, and now the team can start and complete sprints again. Not sure what was wrong with that particular Sprint. Thank you all for your suggestions!

Fabio Racobaldo _Herzum_
Community Champion
January 4, 2023

It's weird but issue is gone :)

Thanks for sharing @alessioLepaya 

0 votes
Trudy Claspill
Community Champion
January 3, 2023

Hello @alessioLepaya 

Welcome to the Atlassian community!

Can you show us the actual JQL of the board filter? 

It must explicitly name the project(s) from which issues will be selected. Trying to filter using Components, Labels, or values for fields that you use in only one project is not the same as explicitly identifying the source project.

If you have an OR clause in the filter, you may have constructed it in such a way that a part of the OR clause is being interpreted as not explicitly identifying the projects.

Trudy Claspill
Community Champion
January 4, 2023

It is also possible that the sprint had an errant issue from some other project that was not within the board scope. Issues outside the board scope can still be added to sprints by directly editing the Sprint field in the Issue.

You could do a search in Advanced Issue Search for issues in that sprint to double check.

alessioLepaya January 9, 2023

I thought the same, but there weren't issues from other projects in that Sprint. Thank you for your input :)

0 votes
Kwame Afreh
Contributor
January 3, 2023

@alessioLepaya 

I will suggest you take a second look at the permission scheme and locate the part that says Manage Sprints. Look at the roles on the right that have been mapped to the managed sprint and make sure the user in question has been assigned one of those roles.

If you are not Jira admin but project admin then you can navigate to the permission by clicking on

Project Settings -> Permissions

Capture.JPG

0 votes
Fabio Racobaldo _Herzum_
Community Champion
January 3, 2023

Hi @alessioLepaya ,

welcome to the Atlassian community!

Please could you check if that user has also Edit Issue permission?

Fabio

alessioLepaya January 3, 2023

Hi Fabio,

Yes, the user has it. I update my question.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events