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

Propagate labels from Epic to children

Mickael Maujean_1oq1td

Hello,

I would like to set up an automation rule to propagate the label of an Epic to all its children issues

The rule return some successes when I update, delete or add label in Epics but nothing happen to the children.

Anything I miss in the above rule ?

Thank you

Accepted answers

Yash_reddy

Hi @Mickael Maujean

Welcome to Atlassian Community

Can you try with Copy Label from Parent instead of Current issue.

Let me know if that worked.

All comments

Yash_reddy

Hi @Mickael Maujean

Welcome to Atlassian Community

Can you try with Copy Label from Parent instead of Current issue.

Let me know if that worked.

Mickael Maujean_1oq1td

Hello @Yash_reddy

Jesus, I've missed that... It works now thank you.

Maybe you can explain what are the differences between Parent, Epic and Trigger issue in that case (I assume all 3 should work for my specific use case)

Thank you again

Bill Sheboy

Hi @Mickael Maujean

Some of the "epic" fields are sunsetting in Jira Cloud, so the "parent" field is used for the entire hierarchy to connect parents and their child issues:

epic
- story, task, or bug
  - sub-task

In rules, you will probably see the language change over time. For now, you can usually use them interchangeably when referring to an "Epic", but still use "parent" for issues and their sub-tasks.

Regarding, "current" and "trigger" issues, the trigger issue is always the same one: the issue(s) provided by the rule trigger. But the current issue changes based on where you are in the rule. That is why the rule in your original question was trying to copy from itself. Here is an example rule to help explain:

trigger: some rule trigger >>> At this point, {{triggerIssue}} and {{issue}} refer to the same thing. In the rule UX, {{issue}} is called "Current Issue".
action: some action >>> No change: they are the same.
branch: on some issues >>> No change: they are the same.
- action: another action >>> Inside of the branch, {{issue}} now refers to the branched-to issue and {{triggerIssue}} remains unchanged.
action: action after the branch >>> Outside the branch again, we are back to {{triggerIssue}} and {{issue}} referring to the same one.

One more wrinkle in this: when a rule updates an issue, that is updated in the cloud, and not yet in the rule. To synch their values, the Re-fetch Issue action may be used to reload the data before the rule steps proceed.

Kind regards,
Bill

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-cloud

automation