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

Sprint Automation: how to automatically assign an issue to a sprint based on Live Date ?


Hi! I've like to find an automation that will assign an issue to a sprint based on due date. 

I have created all my sprints for the next few months, like this: 

- Sprint week 1
- Sprint week 2
- Sprint week 3
- Sprint week 4
- etc
- etc

When issues are created, I would like them to be automatically assigned to a sprint based on their Live date. Which would mean that, if an issue's Live date is updated, that issue would automatically be moved to the correct Sprint. 


1 answer

0 votes
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.
Apr 24, 2023

Hi @Melanie Plourde 

First thing: doing something like this could create some team challenges and rework for the product owner, as people may assume an upcoming sprint's content are fixed, rather than using sprint planning to decide the goal, capacity, etc.  Have you instead considered using the built-in roadmap to place the items?

And...Creating an automation rule like this may not help, as it cannot detect all possible things that impact sprint assignment.  Essentially such a rule would call the REST API to get all possible sprints and then find the correct one...which may not work due to date comparison/filtering of lists.

Additionally, the rule(s) will need to trigger under these conditions:

  • an issue is created with a due date  (This can be detected.)
  • an issue's due date changes  (This can be detected.)
  • an issue's sprint is manually changed  (This can be detected.)
  • a future sprint is changed  (This cannot be detected by a rule.)
  • an issue is moved to another project (This probably cannot be detected by a rule.)

Kind regards,

Suggest an answer

Log in or Sign up to answer