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

How to move "ready for release" tickets back to the backlog after sprint is done?

Cosima Lohse

Hi Community,

I'm a new-be in Jira and our Team has the following issue: We have a scrum board with TO DO - IN PROGRESS - READY FOR TEST - DONE
In the Done column we move all tickets which are closed or ready for release. Problem: sometimes a peson forgets to release the story and if we close the sprint and move on with the new sprint this ticket with the status "ready for release" is out of the backlog, therefore out of sight.

I suggested to do a new column: READY FOR TEST -> READY FOR RELEASE -> DONE

But also in this case my team is worried that after the sprint is done & closed those tickets "ready for release" will be vanished from the backlog.

How can we solve this issue? we want to keep the ready for release tickets in the backlog to finish them in the next sprint and dont forget them

THANK YOU

Accepted answers

Jeroen Poismans

Hi there and welcome to the Atlassian Community!

Some questions for you :-):

Why would you place a "READY FOR RELEASE" issue back in backlog?
What type of status is "READY FOR RELEASE"? Is it a Completed status or ...?

The reason I ask is you said this:

we want to keep the ready for release tickets in the backlog to finish them in the next sprint and dont forget them

What is there left to finish? If there is still work left, is it really "READY FOR RELEASE"?

The other issue with the issues disappearing: When you complete a sprint and there are still issues in a not-done status without resolution, Jira normally asks you what to do with those:

Screenshot 2023-05-03 at 16.50.49.png

Can you elaborate a bit?

All comments

Jeroen Poismans

Hi there and welcome to the Atlassian Community!

Some questions for you :-):

Why would you place a "READY FOR RELEASE" issue back in backlog?
What type of status is "READY FOR RELEASE"? Is it a Completed status or ...?

The reason I ask is you said this:

we want to keep the ready for release tickets in the backlog to finish them in the next sprint and dont forget them

What is there left to finish? If there is still work left, is it really "READY FOR RELEASE"?

The other issue with the issues disappearing: When you complete a sprint and there are still issues in a not-done status without resolution, Jira normally asks you what to do with those:

Screenshot 2023-05-03 at 16.50.49.png

Can you elaborate a bit?

Cosima Lohse

Hi Hi,

thank you for the fast response. in my scrum - team the IT rules are a little different. the story is done, done done, with all the tests, docu etc, but in our IT architecture you need to do an extra release prozess which makes the story closed / released. there are certain constrains coming with that. so yes, you ask the same question like i do: ready for release is not done!!!

In this moment the column DONE contains of: ready for release, closed and resolved. so obviously when the sprint is done, all stories in the column DONE don't move again to the backlog, even though some are not released yet and that is a problem. So maybe it would help if we set up an extra column: READY FOR RELEASE before the column DONE and all the tickets with the status ready for release move into this. and DONE is finally closed / resolved. So if the sprint is closed and Jira is asking what do you want to do with the tickets (not DONE) of the sprint, you can send them back to the backlog or next sprint (like your screen shot)..

-> and here my questions is: if we separate READY FOR RELEASE from DONE we have the chance to move the stories back into the next sprint or backlog once the sprint is done?

Jeroen Poismans

Hi,

Yes, as is shown in the screenshot, you can 😀:

Screenshot 2023-05-04 at 09.09.45.png

Hope this helps!

Cosima Lohse

thank you so much

Welcome!

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

Quick Links

Find more posts tagged with

jira