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 Help: Syncing Attribute of Epic down to Children and Children of Children

David White_8vkl3h

Hello Everyone,

I've done hours of research and I cannot seem to find the answer or create a solution.

Using:
JIRA Cloud,
Next Gen Project

NOT using:
Advanced roadmaps

I've created automation that updates the the children of my epics when the epic is updated. Works great.... however, I realized 2nd level children are not getting updated. I need the change to cascade/waterfall further down the breadcrumbs....

Exampe:

Parent: (Epic) gets Status changed

Automation triggers and updates the Child: (Story) with same status.

BUT the automation is not updating the Child of the Story that gets updated as well. Screenshot 2021-08-18 142154.png

Accepted answers

Bill Sheboy

Hi @David White -- Welcome to the Atlassian Community!

First thing, rules to sync fields are often split into multiple rules to ensure they do exactly what you want and are easier to test/maintain. For example:

Rule detecting field change in epic, which confirms issue type is epic, and then updates stories/tasks/bugs contained within the epic
Rule detecting field change in story/task/bug, which confirms issue type is one of story/task/bug, and then updates any sub-tasks. This second rule uses the Details setting of "Allow Rule Trigger" such that rule #1 can trigger it.

Next from your example, why would you sync status from epic to children to sub-tasks? I could understand the opposite direction...for some scenarios. But updating status seems to invalidate reasons for having the children. Would you please explain further? Thanks!

Best regards,
Bill

All comments

Bill Sheboy

Hi @David White -- Welcome to the Atlassian Community!

First thing, rules to sync fields are often split into multiple rules to ensure they do exactly what you want and are easier to test/maintain. For example:

Rule detecting field change in epic, which confirms issue type is epic, and then updates stories/tasks/bugs contained within the epic
Rule detecting field change in story/task/bug, which confirms issue type is one of story/task/bug, and then updates any sub-tasks. This second rule uses the Details setting of "Allow Rule Trigger" such that rule #1 can trigger it.

Best regards,
Bill

David White_8vkl3h

Hey Bill,

Thanks, I'm not actually trying to update "Status", but instead the custom field/attribute ("SteerCo Priority").

Its a priority number granted by our company's Steering Committee. If they deem something is a Top priority (#1) then all related children need the same priority number applied to them. Likewise, I need to update that number across all children and parents under the epic when it changes (#1 was completed, so now I shift all numbers up 1 slot so 3 becomes, 2 becomes 1, etc).

Ideally I'd like to just update the epics and have it waterfall down to EVERYTHING under all related ticket types regardless of how many parents and children live under the primary epic.

I didn't see the "Allow Rule Trigger" option earlier. I'll go take a peak.

Bill Sheboy

Thanks for clarifying, David! I saw this in your question and it confused me a bit:

Parent: (Epic) gets Status changed
Automation triggers and updates the Child: (Story) with same status.

David White_8vkl3h

Yup, that's on me.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud