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

when we change child tickets fields the changes should replicate on parent ticket.

Chaitanya B

Hi Community,

I'm looking for an automation rule, when we edit the start date on child tickets (task, story) these changes should replicate on parent ticket (epic,initiative)

Thanks

Accepted answers

All comments

Tansu Akdeniz

Hi @Chaitanya B

Sample rule:

automation rule.png

Nic Brough -Adaptavist-

Bear in mind that you probably want to add some more logic to this.

This rule does exactly what you have asked for, but are you sure you want the start date on the Epic to change every time you update an issue?

It won't always, it's entirely possible that someone sets the new date to what the Epic currently has, but Epics are for overarching collections of many issues running over a much longer time period than issues, and it is extremely unlikely that all the issues in an Epic will always start and end on the same date.

Chaitanya B

Hi @Tansu Akdeniz

Thanks for your reply, I created the rule as you said, and the rule audit log says SUCCESS but the changes are not replicated on the epic ticket (parent), what might be the reason

@Nic Brough -Adaptavist- Thanks for your comment rule audit.PNG

Chaitanya B

I got a rule from the Jira automation template library and it worked for me

rule part 1.PNG