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

Issues in the last "Done" column move to the next sprint

hana.let

Hello, I looked through the community on an answer to this and couldn't find an answer, so I'm posting my question with hopes someone can help me out here.

I have one dev workflow and two boards:

- Full flow board: one that shows a progression of an issue from start until it's deployed in production

-Sprint flow board: the other follows an issue within a sprint, from "to do" to "committed"

I have mapped the workflow statuses accordingly with the column statuses, but I am having an issue specifically with the sprint board whereby I put my "committed" status into the last column on the board, and added resolution status to "done", but the "committed" issues in this column still appear in the next sprint. Even when I closed the old sprint they were considered as "completed". So why do they still move over to the next sprint? Is it because "committed" is not technically the last status in my workflow, or because I have another board that follows the full flow from "to do" to production?

Accepted answers

Ste Wright

Hi @hana.let

This shouldn't happen, although I tested it to make sure. This is what I did...

Used a Project with a range of statuses in the workflow
Create a Scrum board, placing the status Committed in the Done column
Create a Kanban board, which had more statuses beyond Committed
Create a sprint, moves stories into the last column, then finished the sprint

^ When I did this, the stories that were in the last column were not added back to the backlog or the next sprint - they're classed as completed. I didn't set a resolution either.

This is the correct behaviour.

I would recommend...

Confirming Committed is in the last column on the Sprint board. It might be useful to have it be the only status in there, and see if that makes a difference.
When running a Sprint, move an Issue to the last column - then check it is classed as completed using the reports (Reports > Sprint Report) prior to closing the sprint.

If the status is definitely in the right column, and/or the issues are not showing as completed - please provide a screenshot of your boards' column configurations so we can investigate further!

Ste

All comments

Vikrant Yadav

Hi @hana.let It seems that "Committed" status is not in Done category. Kindly check "Committed" status category.

Thanks

V.Y

Ste Wright

Hi @hana.let

This shouldn't happen, although I tested it to make sure. This is what I did...

Used a Project with a range of statuses in the workflow
Create a Scrum board, placing the status Committed in the Done column
Create a Kanban board, which had more statuses beyond Committed
Create a sprint, moves stories into the last column, then finished the sprint

^ When I did this, the stories that were in the last column were not added back to the backlog or the next sprint - they're classed as completed. I didn't set a resolution either.

This is the correct behaviour.

I would recommend...

Confirming Committed is in the last column on the Sprint board. It might be useful to have it be the only status in there, and see if that makes a difference.
When running a Sprint, move an Issue to the last column - then check it is classed as completed using the reports (Reports > Sprint Report) prior to closing the sprint.

If the status is definitely in the right column, and/or the issues are not showing as completed - please provide a screenshot of your boards' column configurations so we can investigate further!

Ste

hana.let

Thank you! I think I know what might be the issue. I have the same configuration as you suggested, except, my full flow board is also a scrum board and not a kanban one. Could that be the problem?

Here is the configuration as well, if you could take a look and tell me if anything looks off.

The workflow I'm having issue with:

Dev workflow.png

Sprint board:

Screenshot 2022-03-18 143517.png

Full flow board: Screenshot 2022-03-20 124252.png

Ste Wright

Hi @hana.let

From my testing - it's confusing having two Scrum boards

On the limited board, Issues didn't reappear in the Backlog after the Sprint but...
The Sprint Reports listed them as incomplete, even though they were in the last column

^ This is incorrect behaviour.

You might find though this isn't exactly how your boards behave either, as it depends on the full setup.

Boards are just a visualisation of a filter - and don't own closure, statuses, sprints, etc. You might even find sprints which appear on both boards, etc. It's an abnormal setup from a Jira perspective.

So I would recommend...

Have a Scrum Board for the limited board - issues go into one Scrum Board only
Have a Kanban Board for the full flow

Ste

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server