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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Running latest version of Jira DataCenter.
This is a good starting point: How to update a story's target start and end dates based on the sprint dates using Jira Automation | Jira | Atlassian Documentation
But trying to get the latest sprint end date from a group of stories in an Epic. Reading a single date works, but adding the date.max does not work: {{issue.sprint.last.endDate.jiraDate date.max}}
Hi @Michael Byers -- Welcome to the Atlassian Community!
First thing, I am using Jira Cloud, not Server/Data Center, and so my answer is based on what I know about automation rules.
The Server/Data Center version has the ability to bulk-handle issues for a branch or scheduled trigger with JQL: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html
When you do that, the {{issues}} smart value is available to try to find the latest (last) one.
Kind regards,
Bill
Also tried with {{issues}} (which does return the set) but date.max does not seem to work with sprint dates. For now, I added another IF comparison to keep the largest date in a temp variable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Perhaps also try these expressions to check the date without text formatting as jiraDate:
{{issues.sprint.last.endDate.max}} to check one sprint value per issue, or
{{issues.sprint.endDate.max}} to check all possible sprints for each issue (in case issues were in multiple sprints.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.