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; } } }

Automation: Copy latest "due date" value from stories to epic

Leah Barthelme

Hi everyone,

I would like to create jira automation rules, which help me displaying the true lenght of an epic. Therefore start date and due date of an epic shall be copied based on its associated stories:

1. Epic start date shall be copied from the story with the earliest start date (belonging to the respective epic).

2. Epic due date shall be copied from the story with the latest due date (belonging to the respective epic).

How can I create such automation rules?

Thanks in advance.

Accepted answers

Jack Brickey

Hi Leah, welcome to the Community.

Disclaimer - I have not done this and only briefly played w/ difference between dates using Automation.

Here is what I'm thinking....

Trigger - date field changed
condition - issuetype = story or whatever are your types under the epic
condition - something to ensure you only execute as needed and not on something you don't want to happen
action - if/else block
- if the associated epic has the date field empty then copy date from triggering issue
- else use Compare two dates comparing date of trigger issue w/ epic if trigger is greater then copy into epic else exit

Here is a doc on date functions in Automation - calculating-the-difference-between-two-dates

Sorry that this is not an actual example and hopefully someone w/ handson experience happens along but in the meantime maybe it gives you some ideas to play with on your own.

All comments

Jack Brickey

Hi Leah, welcome to the Community.

Disclaimer - I have not done this and only briefly played w/ difference between dates using Automation.

Here is what I'm thinking....

Trigger - date field changed
condition - issuetype = story or whatever are your types under the epic
condition - something to ensure you only execute as needed and not on something you don't want to happen
action - if/else block
- if the associated epic has the date field empty then copy date from triggering issue
- else use Compare two dates comparing date of trigger issue w/ epic if trigger is greater then copy into epic else exit

Here is a doc on date functions in Automation - calculating-the-difference-between-two-dates

Sorry that this is not an actual example and hopefully someone w/ handson experience happens along but in the meantime maybe it gives you some ideas to play with on your own.

Bill Sheboy

Hi @Leah Barthelme and @Jack Brickey

For your desired outcome, Jack's suggestion works well when you know that the start date and due dates of the child issues (stories) are accurate.

One way to help would be to use another automation rule to set a story's start date when it transitions into an "in progress" status. Due Date seems like a target to me, so if you need an accurate measure of duration, consider setting a custom field in the Epic to LastStoryDoneDate, setting it with another rule when stories are completed.

Please note: if you decide to use multiple rules which could trigger others, select the option of Allow Rule Trigger in the details of the downstream rules. That allows one rule to trigger another.

Best regards,

Bill

Marlene Kegel - codefortynine

Welcome, @Leah Barthelme !

Depending on how you configured your custom fields, your use case should be possible with our Jira cloud app Dynamic Fields for Jira.

If you need help in creating the custom expression for your dynamic field, please get in touch with us. We're always happy to help.

Ayelet Ben-Tzur

Hi @Jack Brickey

I'm struggling with this as well: basically, I've discovered that I implemented this exactly as you wrote BUT there is one major problem -

I have 2 stories, and the earliest start date for example is Jan 18. This was copied to the Epic, and now the Epic will start on Jan 18. So far - great.

Now - I'm changing the start date of the story to Jan 20. This won't be copied to the Epic since the rule copies the date only if it is earlier than the existing date.

So now I have an Epic that starts on Jan 18 when no Story starts on Jan 18.

I'm stuck... Any thoughts?

Jack Brickey

the solution (and i think there is one) really depends on your ability to clearly construct your UC/scenario. Basically, can you construct a simply if-this-then-this-else-if this-then-this-else.... structure.

I am thinking you just need tighter conditions to test what if/else block you need to execute.

With that said, one thing I am always looking out for when constructing automation rules is building fragile rules that can (and consequently will) break. It is hard for me to say if this is the case here. I would really need to fully understand and try to build for myself. I generally like to draw these things out and step back from them and play "what-ifs" to test them out.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

automation