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; } } }

Why are done tasks from previous sprint still listed in current sprint?

Andrey Ivanov_594t32

When I complete a sprint and start a new one, tasks with the Done Reject status from the old sprint are added to the new sprint, although it has already been completed, why does this happen? How to fix this, this never happened before The project is managed by the company

Accepted answers

All comments

Walter Buggenhout

Hi @Andrey Ivanov,

Are your done / rejected statuses mapped to the rightmost column of your board? This is usually the root cause when this happens.

Hope this helps!

Andrey Ivanov_594t32

Yes, of course, I took a screenshot on purpose. Also, if I remove Done from this column, then all tasks with the Done status will disappear on the board, which does not suit me

Walter Buggenhout

If I take a good look at your board, your rejected status is not in the rightmost column, is it? I see it in unmapped statuses on the left hand side.

Also: I did not say you should remove the Done status from your rightmost column. That is exactly where it should be to consider issues as done when you complete a sprint. Issues that get to the Done status / column will remain visible until you complete your sprint, but will no longer be transferred to your backlog or next sprint when you close the sprint.

To make sure rejected issues behave in the same way, you need to map the Rejected status to the same column as where Done is. As long as you don't do that, these issues will keep popping up in the backlog / next sprint when you close the sprint.

Andrey Ivanov_594t32

I already put the Rejected status in the Done column, as a result it turned out that tasks with the Done and Reject status are transferred to the next sprint, and besides, Reject tasks began to appear on the board, which I also don’t need

said kouzibry

What @Joe Pitt said is accurate, please run the following JQL search and see if it returns anything "project = project_key and statusCategory = Done and resolution is empty"

If it returns any issues, you have to either add a closing screen where users set the resolution or automate the filling of the resolution field through post-functions.

You will also have to correct the resolution on all affected issues using automation or an import.

Andrey Ivanov_594t32

As far as I know, if the resolution is not displayed when closing a task, then the task is automatically considered Done (done)

Joe Pitt

The only time the resolution field isn't displayed when closing the issue is if there is a post function setting it. If it isn't being set now, the post function must have been removed.

Andrey Ivanov_594t32

Yes, you're right. I'll now set this function to close automatically, I think this will solve my problem. Thank you!

Welcome!

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

Quick Links

Find more posts tagged with

issue

jira

cloud

jira-cloud

sprint