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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Open/Close sprints with subtasks

Hello everyone,

One of our users has problems when opening or closing sprints, if in that sprint he adds the subtasks to the filter, the button to close it appears disabled and therefore he cannot close it nor can he open new sprints, do you know what it is? can owe?



2 answers

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 27, 2023

Hi Pedro,

There are a couple of reasons this might happen. 

One is that you don't have "manage sprint" permissions in the project that the sub-tasks and their parents are in.

The other is that your issues are inconsistent - the sub-tasks are not sprint items, they do not go into a sprint in their own right, they go into a sprint as part of their parent issue.  It is possible to throw your data into a mess - you can close issues, while having their sub-tasks open.  In this case, Jira does not know whether the issue is open or closed, so it cannot know whether the issue should go into the next sprint or not, and it won't let you close the sprint until you've made the data consistent.  You either need to put all the sub-tasks in the last column on the board, or move the parent issue out of it, back to an open status.

Hi Pedro,

we made the experience that the button to close and start sprints is disabled as soon as the user does not have privileges to manage the sprint on ALL projects included in the filter.

I am not sure about the subtasks you mentioned, but maybe they are part of another project (or at least part of them, if not included for a specific project) and that might already explain the situation :) 

Hope this helps!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events