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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Automation trigger when the sprint value of an issue changes

We have a rule in the project that a story must have a story point estimates when it is in an active sprint. Which means, it is OK to leave the field "Story Points" empty when the issue is in the backlog, but as soon as it is put in an active sprint, the field must contain a value (even if it is zero).

Unfortunately, team members sometimes forget this, so I asked our Jira expert to develop an automation which immediately sends a mail to the person who updated the issue.

Now they tell me that the field "Sprint" is not available as a trigger, even though Atlassian claims that "All fields are available as triggers" Jira automation triggers | Cloud automation Cloud | Atlassian Support.

My next idea was to use "UpdatedDate", i.e. to perform this check when any field has changed, but it seems that this field as well is not available, as it is not an editable field, but automatically updated by the system.

Any ideas how I could identify when a user has updated the Sprint field so I could trigger that automation? Thanks!

1 answer

1 accepted

0 votes
Answer accepted
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.
Nov 13, 2023 • edited

Hi @Martin Härri 

First thing, I am using Jira Cloud, not Server version, and so cannot test my suggestions.

Have you tried using the Field Value Changed trigger and using the Sprint field?  If that does not work...

Please try the more generic Issue Updated trigger, and then check the {{changelog}} smart value to learn if the the sprint field changed.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events