You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We plan sprints way ahead and I would love to have an automation that will move a task to appropriate sprint based on due date.
For example, we have Sprint A (from 1 of Nov till 14th of Nov) and I have created a task with a due date 10th of Nov. It is possible to have an automation to modify the sprint field to Sprint A if the due date is in the timeframe of the sprint?
Thank you in advance!
Are you using Jira Cloud with the Standard or the Premium license? If you are using Premium, there may be something in advanced roadmaps to help with this.
For Standard license, what you ask may be possible with an automation rule, although it would be a bit slow to run and a bit complicated to maintain. Essentially it would need to:
A risk for this rule is it circumvents the scrum framework idea of planning, where the team evaluates the goal and the work to achieve it. Thus you need to figure out a way for the rule to not make changes if the team has places issues in a sprint and then changed the due date later.
Adding some detail for this as the list filtering isn't straight forward - you need to use Advanced Branching in order to have both issue date and sprint date values in scope at same time. https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935
Background: in my team we have non-negotiable recurring tasks that we have automated ticket creation for (all on different cadences, creating new ticket due in X weeks when current ticket goes to done). So we have used an automation that basically follows Bill's suggestion above to put these into the correct future sprint to save time during sprint planning.
The steps in our rule: