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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Trigger Automation when Sprint Dates Added

I'm trying to run a check each time a sprint's start or end date is updated.

The goal is to get issues assigned to the sprint based on a date field of their own.

I have the automation working, but only with a trigger of Sprint started as the start/end dates of the sprint are not populated until after it is created.

Any ideas on an alternate trigger to use that would allow me to access sprint.endDate and other sprint smart values?

2 answers

1 vote
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.
Aug 09, 2022

Hi @Ellis Coon 

First thing, I am assuming that you are trying to automatically assign issues *before* sprint planning, and that during sprint planning the team would make adjustments based on capacity.

On to your question...

There is an open suggestions to add a "sprint updated" trigger, which you may watch/vote for to see progress:

Until that becomes available, one work-around would be below.  Please note I have not tried such a rule to solve this specific problem.

  • a rule triggered on an issue change of Due Date, or a scheduled/manual trigger rule
  • which calls the REST API using a web request to gather all the future sprints for the board
  • find the relevant sprint for the Due Date using list filtering, and
  • add the issue to the sprint

Depending upon how this rule is implemented, it could take several seconds to run.  For example, if this happens based on an issue Due Date change, that would be several seconds per issue.  If instead this ran on a schedule, it may be possible to use just one call to the REST API to update several issues.

Kind regards,

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 09, 2022

Hi @Ellis Coon , those dates are not accessible to query. I don't quite understand your goal. Are you saying you wish to derive what sprint an issue guests assigned to based upon the issue's due date?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events