The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

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

Jakub G
May 16, 2017

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Thomas Schlegel
Community Champion
May 16, 2017

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.

Jakub G
May 16, 2017

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

Jakub G
May 16, 2017

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

TAGS
AUG Leaders

Atlassian Community Events