Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation rule for issue *removal* from active sprint Edited

Which automation rules should be used to trigger an action when an issue is *removed* from an active sprint?

This is easy for *addition* to an active sprint:

  • When: Value changes for `Sprint`
  • If: Issue matches JQL `Sprint in openSprints()`

I've tried several variations for the sprint-removal case, like:

  • When: Value changes for `Sprint`
  • If: Issue matches JQL `(Sprint is EMPTY OR Sprint not in openSprints()) AND {{fieldChange.from}} in openSprints()`

But I haven't found a way for Automation to play nicely with previous values of a multi-value field. `fieldChange.fromString`, `changelog.sprint.from`, etc... no dice.

Is this possible?


1 answer

1 accepted

3 votes
Answer accepted

Hi @Alex Ball 

There are suggestions in the Code Barrel backlog to detect sprint scope changes as a trigger, and Jira backlog to do so with JQL: 

I believe there is a ScriptRunner function to detect scope changes, if you have that add-on: removedAfterSprintStart.

Without those things...

Have you tried to shorten your JQL condition?  This worked for me:

  • Trigger: value changes for Sprint
  • Condition If issue matches JQL: 
key = {{issue.key}} AND Sprint IS EMPTY OR Sprint NOT IN openSprints()
  • Action: log the issue was removed from the sprint


Best regards,


Thanks, Bill! I'll keep tabs on those backlog issues.

Unfortunately, `Sprint is EMPTY OR Sprint not in openSprints()` doesn't quite do it, since we put "top of backlog" issues in four future sprints, each representing a different category (infrastructure, sales requests, bugs, etc.) for better visibility into sprint budgeting. Thus, that rule would trigger when moving an issue from one future sprint to another, which we don't want. AFAIK this means that we need access to the previous sprint value, to ensure that the issue was removed from the *active* sprint.

Bit of a niche case, I know. I'll give ScriptRunner a spin shortly.

Like Bill Sheboy likes this

Hmmm... I tried moving from the active sprint to both the backlog and future sprints, which worked for me.  The problem edge case is when you have parallel, active sprints.

One work-around for the future-to-future scenario: when a sprint starts, mark all issues that were in scope at that time (comment, custom field, etc.) using a different rule.  Then in your removal-detect rule, add a condition to look for that that marking so you wouldn't continue for the move of future sprint A to future sprint B.  (This technique also helps with reporting scope changes over time.)


Like Alex Ball likes this

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you