nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"done" Issues are moved to next sprint when closing the sprint

Itay Keller_vqtase

We have this strange behavior with issues when closing a sprint.

Our "done" status is in green color in the workflow.

When we are closing the sprint , we have a notification that X issues are done and Y issues will be moved to the next sprint.

And yet, after we close the sprint, many (if not all) of the "done" issues are moved automatically to the new sprint.

Here is an example of such issue that was marked as "done" and yet was moved to the next sprint. time is descending:

Accepted answers

Alexey Matveev

Hello,

If an issue is not in the most right column of your board, then the issue is considered as not complete.

All comments

Alexey Matveev

Hello,

If an issue is not in the most right column of your board, then the issue is considered as not complete.

Itay Keller_vqtase

And if in my view there is no column to "done" issues?

Ollie Guan

Hi @Itay Keller,

Could you take a picture of your Kanban Columns configuration, similar to the following

Alexey Matveev

You should add such a column. And it must be the most right column

Itay Keller_vqtase

Here you go:

Itay Keller_vqtase

So Jira is actually ignoring the status of "done" and only checks the column they are in?

Ollie Guan

As mentioned by Alexey, when the sprint is completed, the issue in the most right column is considered to be the completed task, and the other columns will be moved back to the Backlog.

Steven Rho_vc37dc

Hi @Ollie Guan - I have a similar issue where issues are getting moved into the next sprint even though they're in a done status. The kicker is that they're in the far right column of the board. Any thoughts?

FYI we number our sprints with odd numbers. Don't ask why.

Margo Smith_89uhj2

I figured it out. Go into your "Board" and click on the done task. Change the status to "To Do" then move it back to "Done". A green check mark will then appear and finally that task will be considered completed and not move into the new Sprint. It is the equivalent of turn it off and turn it back on.... A very odd bug that Jira Next-Gen employees should really fix.

Valeesha

Thanks for this!

I just had to move 26 issues manually between Done - To Do - Done for the green check mark to appear.
Very frustrating that this is happening. Unsure how, but I'm going to monitor the Done tickets over our next sprint to figure out why not all tickets have a green check mark.

William Seamon (BTC Power)

We are having the same problem. We have a larger workflow and moving the Done tickets to an active status (Done check mark disappears), then back to Done (Done check mark reappears), before closing the sprint didn't stop the Done tickets from going to the next sprint. We have a Duplicate status that is also considered as done. Setting tickets to Duplicate did stop them from transferring to the next sprint.

It is very frustrating and since only our administrator can talk to Atlassian and he is on a different continent.

Arnoud vd Zwan

I consider this a bug, It should not matter if an issue is in the right collumn or not. Done is Done (or any other resolution).

Nic Brough -Adaptavist-

You should stop thinking of it as a bug - it is working as intended.

James Finlinson

Can you help me understand what the meaning of a "Done" status is, if it doesn't mark my issues as done?

We added in an "abandonded" status in the "done" category to indicate the tasks that we've given up on. We want them categorized differently because we may want to review these at a later date to resume work; however, for all intents and purposes, the team is "done" with it, and I don't want it moving on to a new sprint.

Can you show me another way to organize this information in Jira that would accomplish this purpose?

Your input would be much appreciated.

Arnoud vd Zwan

Why would you need a functionality in jira where tickets which are in a "done" status go to the next sprint ?

Jeremy Lambert_g8qdh3

That tip worked for me! Thanks for sharing

Rakesh Murali

There's a requirement on Jira that the Done column be the last (right-most) column. Pl check columns and statuses in project settings. Jira also gives a tip saying the same. Then the tasks move out of the sprint. However, in our case, sprint burndown chart doesn't get updated.

Arnoud vd Zwan

I did resolve the issue after some time. It does make some sense because one sprint board is one increment / iteration. At the end of the board (last column) stuff goes to production, so it is finished. My problem occurred because the end of the board was not finished, but the item went to another board. So Jira thinks it is not finished which is actually true.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud