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

If I label an Epic can I automate that label to go to all the tasks related to that epic?

sofia.pedro

Before installing Automation for Jira, I want to know if it is possible to automate the labels that an epic has to all the tasks related to it.

For example, I have a label on an epic "testing". Can I automatically make sure any task linked to this epic will also have the "testing" label?

Accepted answers

Bill Sheboy

Hi @sofia.pedro -- Welcome to the Atlassian Community!

Yes, you can copy the label to the tasks associated to the epic. And, the automation rules feature is already included with JIRA Cloud, so there is no need to install or add it.

As an example, your rule would be:

Trigger: field value change for Labels
Condition: issue type equals Epic
Branch: for all the stories or issues in the Epic
- Action: edit the Labels field, copying it from the Epic

To get started and learn more about the automation, please review this documentation:

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

Best regards,

Bill

All comments

Bill Sheboy

Hi @sofia.pedro -- Welcome to the Atlassian Community!

Yes, you can copy the label to the tasks associated to the epic. And, the automation rules feature is already included with JIRA Cloud, so there is no need to install or add it.

As an example, your rule would be:

Trigger: field value change for Labels
Condition: issue type equals Epic
Branch: for all the stories or issues in the Epic
- Action: edit the Labels field, copying it from the Epic

To get started and learn more about the automation, please review this documentation:

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

Best regards,

Bill

sofia.pedro

Hi Bill,

Thanks for this response I was to automate copying down labels from Epics to all the stories or issues in the Epic!

However, I am having issues with two different scenarios and was wondering if you could help me.

If I add a new issue under an epic it does not copy down the labels from the epic. It only copies the labels in already existing issues or stories
If a label is removed from an epic it does not remove if from the issues within the epic. In other words, nothing changes in the issue's labels field if the Epic label is removed.

Best,

Sofia

sofia.pedro

Hi @Bill Sheboy ,

Thank you for your response! I was able to copy down the labels from epics to all stories or issues in the epic that are already existing.

However, I have problems with two different scenarios that I was hoping I could get your help with.

how do I get the Labels to copy from the Epic when the issue is created or the issue is associated with a new epic? Right now when a new issue is created within an epic it does not automatically copy down the epic's labels, only with existing issues.
When a label is removed from an epic, how do I also remove it from all issues within the epic without overriding the other labels that the issue contains? In other words, as of now when a label is removed from an epic nothing happens with the issue's labels field.

Thanks again for your help.

Best,

Sofia

Bill Sheboy

Hi @sofia.pedro

Sorry for the long answer, as I want to try to answer all of your questions...

At this time, you cannot iterate over a smart value field list, like Labels, to process the values separately in the branch. That feature is in the backlog here:

https://codebarrel.atlassian.net/browse/AUT-546

Let's look at your scenarios to see what you can and cannot do at this time:

When an issue is created... You could create a rule
- Trigger: issue create
- Condition: Epic Link is not empty
- Action: copy Labels from epic
When the epic changes for an issue... You could create a rule
- Trigger: field change to Epic Link
- Condition Epic Link is not empty
- Action: copy Labels from epic
When a label is removed from an epic... I believe the rule I described will handle that case. It did in my testing.
- Trigger: field change to Labels
- Condition: issue type is Epic
- Branch: for stories and issues in Epic
  - Action: copy labels from Epic (triggering issue)
When an epic's labels change, do not wipe out unrelated child issue labels...
- This one cannot be handled until AUT-546 is implemented
- A work around would be to consider what you are using Labels to represent, and decide if the Label values added for the children could be represented in another way, such as with Components or a Custom Field.
- A different work around would be if you *know* possible values for children labels, use an If/Else structure to test for them, copy the Epic Labels, and then re-add the value. If you do not know the possible Labels, this will not help.

Best 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-software