Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Transition stories back to to-do when stories are moved out of a sprint

Rania Haddadin August 5, 2024

Does anyone know of an automation rule that will transition stories/tasks/defect, back to the to-do status if it's moved out of a sprint?

2 answers

1 accepted

1 vote
Answer accepted
Bhanu
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.
August 5, 2024

Hi @Rania Haddadin

You can try something like this:

Trigger: Field Value Changed

Condition: Jql to check if the issue vbelongs to the openSpring (Example: Project = JIRA and sprint not in openSprints())

Action: Transition Issue

Hope this helps!

Rania Haddadin August 5, 2024

It worked, thank you so much

Like Bhanu likes this
1 vote
Bill Sheboy
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.
August 5, 2024

Hi @Rania Haddadin 

There are two steps to building a rule like this:

  1. confirm the issue was in the open / active sprint
  2. confirm the issue is no longer in the open / active sprint

The first part is required to prevent updating issues which are modified in the backlog, and not in the current sprint.  It may be done by either using the changelog fields to check the prior sprint values, or to initially "mark" (e.g., with a Label value) all issues in the sprint using another rule, triggered on Sprint Started...then check that "mark" before transitioning issues.

The second part may be checked with a JQL condition of sprint NOT IN openSprints().

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events