Forums

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

Is there a way to be alerted when anyone moves an item out of the current sprint?

Lily Tucker-Ha January 12, 2023

Hi,

please can someone help; Is there a way to be alerted when anyone moves an item out of the current sprint?

I've been trying to set this up myself for a while but I'm getting stuck because I'm using the "Value changes for" trigger; i.e.

Trigger: "when value changes for Sprint"

Branch: for issues in the sprint

Then: Send email

However, the rule fails to run with the error :

Action details:
["10099"]
Branch rule / related issues
Can't branch rule as it requires a sprint in the context for this option. More than likely you have a trigger that isn't sprint related.
Which makes me think I'm not using the correct trigger, but there isn't one I can see that is relevant. At the same time, I know you can't use "current" or "active" sprint on filters, so maybe that's why I can't specify changes to the active/current sprint?

 

Maybe there's an easier way to do this other than automation that I'm missing completely. Please help?

Thanks,

Lily

 

1 answer

1 accepted

0 votes
Answer accepted
Mark Segall
Community Champion
January 12, 2023

Hi @Lily Tucker-Ha - The big thing is that you need to be able to evaluate whether the original or new sprint value was for the current sprint.  Try something like this:

 

  • TRIGGER: Field Value Changed (Sprint)
  • ACTION: Lookup Issues
    We'll first make sure that the issue hasn't been pulled into sprint (unless you want that captured too)
    • sprint in openSprints() AND key = {{Issue}}
  • CONDITION (Advanced)
    • {{lookupIssues.size}}
      Not Equals
      1
  • ACTION: Lookup Issues
    Now we'll figure out the current sprint
    • sprint in openSprints()
  • CONDITION (Advanced)
    • {{fieldChange.from}}
      Equals
      {{lookupIssues.first.sprint.id}}
  • ACTION: Send Email
Lily Tucker-Ha January 12, 2023

Hi @Mark Segall wow thank you, I may or may not have followed the logic, so thank you for laying it out so simply for me. This worked a treat!

Like Mark Segall likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events