How to move tasks with custom statuses to next sprint?

[Amulya Sankara]

Hi,

I have created custom statuses for my Software Team, like Code Review, Acceptance, Test Env, etc. All these custom statuses are assigned to 'Done' status as per our internal workflow. 

Now when we complete one sprint, we want to also move issues with the custom statuses to the next sprint. This is because although they are assigned to 'Done', we need the issues to reach the final status of 'Done'. 

However, Jira only allows the open issues to be moved to the next sprint. Since the custom statuses are assigned to 'Done', Jira considers them part of the Done column in the board. For analysis and reporting purposes, we would like to have the custom statuses to remain in the 'Done' column. 

So is there a way to create a setting where I can move all issues to the next sprint, i.e all issues without the final 'Done' status?

Thanks!

[Vishal Biyani · Accepted solution]

@Amulya Sankara 

You can try below automation:

Trigger

Sprint Completed (Specify the board)

Branch 

For each issue in the sprint

Add If

check issue field condition (status in ("Code Review", "Acceptance", "Test Env"))

Edit Issue

Select Field as Sprint and in the box select Next Sprint

[Amulya Sankara]

Great, this looks like a good option. Thanks, I will try this!

[Vishal Biyani · Accepted solution]

@Amulya Sankara 

in your sprint board view, what is the statuses mapped to right most column?

if you remove your custom statues from right most column, I believe, you should be able to achieve your use case when closing the sprint. Issues with these statuses will be moved to next sprint.

Check and let me know if this works for you

[Amulya Sankara]

Yes I thought of this. However, we would like to keep the custom statuses in the right most column since they all essentially are assigned to Done and this will mess our sprint analysis. 

Thanks for the suggestion! 

[Nikola Perisic · Accepted solution]

Hi @Amulya Sankara 

One of the ways you can actually do this is bulk transition and moving issues to the next sprint:

• Issues > JQL 

Query: status in ("Code Review", "Acceptance", "Test Env") AND Sprint in openSprints()

Then you select three dots and select Bulk Change.

You would then select Transition issues to move them to the next sprint and assign correct values.

[Amulya Sankara]

Hi, 

This sounds like a good solution. Do you know if I can add any Jira Automation for this, so that I can do this at the end of each sprint?

[Nathan Phillips]

Hello @Amulya Sankara,

Below is a direct link to our smart values for automation, specifically smart values for Sprints:
https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#:~:text=rule%20actor%20user.-,sprint,-Added%20by%3A%20Sprint