Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,415
Community Members
 
Community Events
185
Community Groups

Set Epic Start and Due Date to earliest/latest Child Dates

Edited
Roman Kastner
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 08, 2023

Hi,

I want to have an automation to do the following:

The type of trigger does not really matter (manually or field value change is possible), but it should be executed on an Epic.

The automation should get the earliest Start Date of all child Issues under an Epic.

Then the Epics Start Date should be updated with this earliest Start Date.

Analogously I will need the functionality for the Due Date.

 

A screenshot and possible queries would be much appreciated!

Thanks in advance

1 comment

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 09, 2023

Hello @Roman Kastner 

Welcome to the Atlassian community.

You could use the Field Value Changed trigger to monitor the Start Date and Due Date fields for changes.

You would follow that with an Issue Field Condition to confirm that the issue is not an Epic or a subtask.

You would follow that with a For Branch / Related Issues / Epic (parent) step

Within the branch you could use the Lookup Issues action to retrieve all the child issues of that Epic via JQL where the field you monitored in the Trigger (Start Date, or Due Date) is not empty, and order the results by that field so that the first issue listed would have the date you want to copy to the Epic. 

i.e.: "Epic Link" = {{issue.key}} and "Start Date" is not empty ORDER by "Start Date" asc

You would add an Advanced Compare Condition to confirm that there was at least 1 issue in the result set.

- First Value: {{lookupIssues.size}}

- Condition: greater than

- Second value: 0

The next step would be to update the Epic's Start Date field with the Start Date value from the first issue in the results set using the Edit Issue action.

- Field to update: Start Date

- Value: {{lookupIssues.first.Start Date}}

 

Repeat the Lookup Issues, Advanced Compare, and Edit Issue actions for the Due Date field.

Screen Shot 2023-05-09 at 4.27.57 PM.png

Roman Kastner
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 10, 2023

Hello Trudy,

thank you so much, it works.

 

Best regards,

Roman

Like Trudy Claspill likes this
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 10, 2023

You're welcome.

In the future, you may want to post questions in the Questions board rather than the Discussion board.

Like Roman Kastner likes this

Comment

Log in or Sign up to comment