Carry only unfinished work with specific status to next sprint when closing the sprint

upinder.kaur.paul December 10, 2021

Hi team

When we close the sprint, only user stories with 'DONE' status remain in current sprint, other stories are considered as unfinished work and they are moved to next sprint.

We have requirement that user stories with status like 'Product review' & 'Ready for SIT' or 'IN SIT' which should not move to next sprint while closing the sprint. 

Basically stories with DONE, PRODUCT REVIEW & READY for SIT or IN SIT status should remain in current sprint and stories from current sprint with statuses  (in progress, to-do,
in development etc.)  i.e. other than above should be moved to next sprint.

Can you please let me know if there is any configuration through we can achieve this?

 

Thanks
Upinder Paul

 

 

2 answers

1 accepted

0 votes
Answer accepted
Ankit Srivastava
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 10, 2021

Hi @upinder.kaur.paul ,

As Jack suggested you need to move all the status to the Done Column (It should be right most column of the board), So whenever you will complete the sprint it will only ask of the remaining column's issue to move to next sprint.

Please refer the screenshotAtlassian Answer1.JPG

Hope this will help.


0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 10, 2021

Hi @upinder.kaur.paul , To be clear when you complete a sprint the issues in the right most column are considered complete and will be used in all of the metrics/reports. If you are wanting to have those additional status considered to be done then they must be mapped to the right most column. Otherwise Jira considers all other issues incomplete and they will be moved to either the backlog or the next sprint based on your direction.

Suggest an answer

Log in or Sign up to answer