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

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

Rania Haddadin

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?

Accepted answers

Bhanu_ihv087

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!

All comments

Bhanu_ihv087

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

It worked, thank you so much

Bill Sheboy

Hi @Rania Haddadin

There are two steps to building a rule like this:

confirm the issue was in the open / active sprint
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

Welcome!

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

Quick Links

Find more posts tagged with

automation