Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Transitioning "Ready to Work" to "Open" when removing from active Sprint, but NOT closing Sprint

Mark Bodha June 17, 2025

Hi All,

I'd like to use automation to ensure all tickets in the active sprint and waiting to be worked on are set to Ready to Work – to distinguish from Open in the Backlog.

Automating the transition when starting a sprint or adding tickets to the active sprint works fine (see rules structure below).

When a ticket is removed from the Sprint, however, I would like to set its status back to Open.  When a Sprint is closed, however, I'd like in-flight tickets (In Progress, Testing) to retain their values when they are moved into their new, upcoming Sprint

I originally created a rule to transition any ticket removed from openSprints() back to Open : when sprint value changes, if sprint not in (EMPTY, futureSprints()) then transition to Open.

The difficulty I'm having is when we close (i.e. legitimately finish) a sprint and move any incomplete tickets into the next upcoming sprint – i.e. a futureSprints(), this also triggers the rule.  This means all those in-flight tickets get reset back to Open,  which is inconvenient – we'd like to carry their existing status in their new, upcoming Sprint.

Is there a way I can ignore tickets that were in the just-closed sprint?  Or a way to achieve the Ready to Work idea?

Thanks!

Mark 

 

Automations to set Ready To Work when starting or adding tickets to a Sprint.

Start of Sprint trigger:

  • When Sprint Started in [myboard] 
  • For Issues in the Sprint AND Status = Open (i.e. not already in-flight)
  • Transition to Ready to Work

Adding tickets to an open Sprint:

  • When Value changes for Sprint
  • If Sprint in openSprints() AND Status = Open
    • Don't actually need the status portion, but just to be clear to myself it only applies to tickets from the Backlog

3 answers

0 votes
Mark Bodha June 23, 2025

Thanks both, I'll give these a try 👍🏽

0 votes
Gor Greyan
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.
June 17, 2025

Hi @Mark Bodha
Try the following condition, maybe it will fit for your case.

sprint not in (openSprints(), futureSprints()) AND
sprint WAS IN openSprints() AND
status = Ready to Work

Mark Bodha June 23, 2025

It appears the "Was in" operator cannot be used with Sprints:

https://jira.atlassian.com/browse/JRASERVER-39256

0 votes
arielei
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.
June 17, 2025

Hey @Mark Bodha 

You can do the following adjustments to your automation:
Trigger: When Sprint value has changed

1. Add a "Delay" action for 2-3 seconds.

2. Re-fetch data

3. Check if Sprint value does not exists 

 

and keep the rest.

This way it will catch only work-items that were removed from the sprint.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events