Hi all , I want to automate start date and due date from linked issues to epic hierarchy * story 1 has start date Jan 1st' 22 & Due date Jan 31st' 22 * story 1 has start date Feb. 1st '22 & Due date Feb. 28th ' 22 * story 1 has start date March 1st' 22 & Due date March 31st 22 So in these linked issues the minimum date is Jan 1st'22 and Maximum is March 31st '22 So the Epic hierarchy should automatically update the minimum date is Jan 1st'22 and Maximum is March 31st '22, Considering child linked story issues Kindly help with automation rules

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Auto populate start date (minimum) and due date (maximum) of linked issues ,for parent Hierarchy

sharath krishna

Hi all ,

I want to automate start date and due date from linked issues to epic hierarchy

story 1 has start date Jan 1st' 22 & Due date Jan 31st' 22
story 1 has start date Feb. 1st '22 & Due date Feb. 28th ' 22
story 1 has start date March 1st' 22 & Due date March 31st 22

So in these linked issues the minimum date is Jan 1st'22 and Maximum is March 31st '22

So the Epic hierarchy should automatically update the minimum date is Jan 1st'22 and Maximum is March 31st '22, Considering child linked story issues

Kindly help with automation rules

Accepted answers

Bill Sheboy

Hi @sharath krishna -- Welcome to the Atlassian Community!

Are you using Jira Cloud or the Server/Data Center version? The version you are using will determine how to solve this...

For Jira Cloud, trigger your rule on a change to Start Date or Due Date, then gather the sibling issues with the same epic parent, using JQL and Lookup Issues. You may then branch to the epic parent to make the edits, using the values: {{lookupIssues.Start date.min}} and {{lookupIssues.Due date.max}}

For Server/Data Center, instead try using the bulk issue features of rules as that version does not have Lookup Issues.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @sharath krishna -- Welcome to the Atlassian Community!

Are you using Jira Cloud or the Server/Data Center version? The version you are using will determine how to solve this...

For Server/Data Center, instead try using the bulk issue features of rules as that version does not have Lookup Issues.

Kind regards,
Bill

Tomislav Tobijas

Hi @Bill Sheboy,

Quick question - I've just tested {{issues}} within bulk issue features, but something seems a bit off here.

So, I would like to get the same result as mentioned in the original question and I've constructed the following rule:

Basically, upon change of the End date (on stories), go through all issues with the same epic, and try to get max End date value.
However, I've tested it a bit (with 2 stories within an Epic) and it seems that

{{issues.End date.max}}

only looks at another issue within the JQL results. For example, if I update the value on UOPR-3505, the max result will always be a date from OUPR-3506 (and vice versa).

Am I missing something here or? This was also just for testing purposes, but I'm also not sure even if I get the right value, how could I update Epic End date with right value? There's no Create variable action that I could use either. Maybe to store this 'max' value somewhere (new field or maybe even a webhook)?

Bill Sheboy

Hi @Tomislav Tobijas

First thing: I am using Jira Cloud, not Server/Data Center, and so cannot verify my suggestions for that tool.

Next, it appears Atlassian is implementing Create Variable for Server/Data Center, and you can follow progress on this suggestion: https://jira.atlassian.com/browse/JIRAAUTOSERVER-22 They are also implementing Lookup Issues for Server/Data Center, and that could also solve this scenario: https://jira.atlassian.com/browse/JIRAAUTOSERVER-53

Back to your question and rule...

I note you have a couple of re-fetches in there. I have only used this with the Issue Create trigger (as it runs very fast) and when there are changes in a rule. You have neither of those, so perhaps remove them. Honestly, I am unclear what re-fetch inside of a bulk-handling branch would mean!

Here is what I wonder is happening...The rules engine appears to be built to prevent collisions and looping errors. And so JQL branches automagically exclude the trigger issue to prevent problems.

A work-around could be divide and conquer, with two rules:

One rule detects an End Date change in a story with an Epic parent, and then branch to the Epic and make a change (like a specific comment) to trigger rule #2
Another rule has "Allow Rule Trigger" enabled in the details, and is triggered on a comment. Now a branch to the child issues should include all others when you look for the maximum End Date.

Kind regards,
Bill

Tomislav Tobijas

Yeah, I'm already on the watch list for those suggestions, but cheers for sharing the links! I'm also using cloud automation way more than server so I came here in the hope to find some help 😄

And so JQL branches automagically exclude the trigger issue to prevent problems.

Lol, lovely 😅 I never knew this was the case... I've just tested it and you're right there. You cannot even 'force' the branch to include a trigger issue (I've tried adding OR key = {{triggerIssue.key}}, but no luck there).

Anyway, I've modified your suggestion a bit. Instead of placing a comment on an Epic, I've just used a webhook from the trigger story and then created another automation rule to run on the issue Epic. Nothing fancy, but this would remove unnecessary information/comments on Epic plus notification spam.

So, now getting the right results from

{{issues.End Date.max}}

but how can I get/write down this value to the parent issue as I'm currently in the branch that only looks at child issues?

Btw, thanks for the help and fast reply!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

automation