Closed tasks are moved to the new sprint, each time a sprint is finished Edited

We have a self-hosted JIRA instance.

I've noticed that every time a sprint is closed and new one is created, many tasks (US/bugs) are moved to the new sprint, even if their status is "CLOSED".

What are we doing wrong? How to get rid of those annoying forever-alive tasks?

 

jira1.pngjira2.png

jira3.png

1 answer

0 votes

Hi Jakub,

do you have the Closed-state as last (= most right) column on your task board? 

Issues that are not in the most right column of the board are moved to the next sprint.

When I click "View Workflow" next to "CLOSED", it displays a graph like this...

So I guess only "ACCEPTED" tasks are considered truly finished, right?

Is it possible to have both "ACCEPTED" and "CLOSED" as terminal states? (I don't admin the JIRA, I don't really know all of those things)jira5.png

When I click "Active sprints" in the menu on the left, I see a board like this, and yes, most of the tasks are in "Done" column (rightmost one)

jira6.png

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,175 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot