Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

User cant manage sprint although having permissions Edited


There´s a project that have some boards. One of them, jql query include other project. 
This user has manage sprint permission (current project, and involved project) also is a Project Admin in current projec, but he is not enable to complete sprints any.

The curious thing, is the user is having this problem only on this project. Hi can complete sprints in others projects.

2 answers

1 accepted

0 votes
Answer accepted

Hello @Sofia Quintero 

Can you paste a copy of the Filter used in the board?

Can you run a search for all issues that have Sprint values that match the sprints in the board? It is possible that an issue in a project where the user does not have the Manage Sprints permissions has gotten assigned to a sprint in this board. You would not see that rogue issue on the board if it doesn't fall within the constraints of the board filter, but JIRA does not prevent a user from adding an issue outside of the board to the sprint. That could be done be editing the issue and changing its Sprint field.

Hello @Trudy Claspill  the problem is for all the bords in the project, there are some of them that query only include current project issues and others that involved others projects. 

I mean, he can´t manage sprint for a board that include only project issues. He has permission.

Here´s the query from boards

Board project = ERPSP AND status not in (cerrado, Closed) OR project = "Tribu Core" AND component in ("Finance & Operations") ORDER BY Rank ASC

project = ERPSP AND issuetype = Épica AND status not in (cerrado, Closed) OR project = "Tribu Core" AND component in ("ERP Finance & operations") ORDER BY Rank ASC

project = ERPSP AND labels = collector-b8904a84

Thanks for answer @Trudy Claspill 

Hello @Sofia Quintero 

Try executing an advanced search for any issues that have been assigned to sprints in the boards where the issue is not in one of the specified projects; i.e.

Sprint in (<sprint1>,<sprint2>,<sprint3>) and projects not in ("Tribu Core",ERPSP)

That should reveal if there are any issues from other projects that have been erroneously assigned to sprints in these boards. 

If there are such issues, remove them from your boards' sprints and then see if the user can manage sprints.

Hello @Sofia Quintero 

I see you marked my answer as Accepted. Did the problem get solved? If so, what did you find was the root cause?


It was a pretty silly mistake. The components that filtered the two queries did not exist. And I don't know why this also affected the board that filtered a single project and without components. But it was as you said, the problem was in the filters.

0 votes
Jack Community Leader Jan 12, 2021

on the board spanning multiple projects, the user must have manage sprint permissions for all projects referenced in that one board. 

Hello @Jack , that´s the problem, he already has manage sprint permisions in all involved projects on board

Jack Community Leader Jan 12, 2021

Thanks for clearing that up for me Sofia. And does this individual have all the other typical issue permissions that might be involved in managing the board, e.g. close issues, transition issues, schedule issues? Granted not all permissions are required to manage sprints but sometimes there are underlying rules that are associated w/ workflows or automation that could be causing a conflict. If nothing is obvious what I would do is to perform a bit of sleuth work. For example you might have the user create test boards in each individual project, create test issues in each project, add them to sprints, move them thru the sprint and finally close the sprint. I suspect you will hit one project that reveals the smoking gun. Of course I would go thru the the inspection of all permissions in all projects first. Other questions, is this a new issues or was it working before? are there other users that can closed a sprint?

Thanks for the answer @Jack . Yes it does, the user has all the other typical issue permissions that might be involved in managing the board. Yes it seems to be a new problem, and there aren´t other users  with the same problem. And also the user is having the problem only in one project. He can manage sprint on others.

Jack Community Leader Jan 12, 2021

so if it is only one project they have an issue with then there sure seems to be a permissions issue. it could be a bug but I really don't expect that to be the cause here. Maybe some Issue Security conflict? Are you using Issue Security in that project, just a last minute obscure thought. If it was working before I suspect someone has changed something.

i've just checked, and there´s no security scheme for this project. Just for be sure, I created the same scenario in test environment but there was no problem.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

130 views 2 7
Read article

Community Events

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

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you