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
Currently, I have this hierarchy:
I want parent issues to inherit the latest due date of their child issues.
A story should inherit from a subtask, an epic from a story, an initiative from an epic, and a theme from an initiative.
For instance, if a story has 10 subtasks with due dates, then the story should inherit the latest due date of the subtask and this should be applied for all levels. How can I achieve this?
If it is possible to set up automation for that, please share the automation flow.
Thank you in advance
You can accomplish that with this rule. In my example I an using the Start Date field, and setting the value to be the earliest value among the child issues.
To set it to the latest value you would use "max" instead of "min".
You also need to make sure that you have this box checked on the Rule Details page:
Additionally, if at any level an issue can have children in a different project, then you have to make the rule a multiple project scoped rule and include in the project scope all the projects where child issues might exist. Multiple Project scoped rules can be created only by Jira Administrators from the Global Automations page.
Check out this post:
They are talking about different fields, but I suspect the same logic might apply to your use case.
Hope it helps,
Adding on to Dave's suggestions...
This is a lot of issue type levels to roll-up, and so I recommend defining your assumptions before writing any automation rules for this. That will help to identify test cases and limitations to the solution.
You could also consider limiting the scope, such as only use the Due Date at some levels. That would reduce the complexity and may still provide you the benefits you want.