You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
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:
To get started and learn more about the automation, please review this documentation:
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.
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.
Thanks again for your help.
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:
Let's look at your scenarios to see what you can and cannot do at this time:
Hi @Bill Sheboy ,
Thanks for your detailed explanation,
In regards to 1 & 2, it is impossible because choosing Epic Link is not appearing for us. We also want to be able to NOT copy certain labels as part of these scenarios.
As for 3 & 4, we are adding to the existing values rather than replacing the label.
I apologize for my error: it appears that it is not yet possible to trigger a rule based upon an Epic Link change. Here is the ticket for that issue:
Regarding replacing existing labels, with the edit action you can select the ... to the right of the field and select Add/Remove, and select the Epic as the source to add from.
To back up you your original question, I wonder what information you are storing in Labels and if there is another way to solve the problem. You noted "testing" but that seems more like a status. What can you describe about the problem you are trying to solve?
Hi @Davis Moes
That branch you note would not find the sub-tasks. You could either:
So I created two rules, first one is for updating the story, second is for updating the subtask. For some reason, the second rule (subtask rule) does not update the "Labels" field after the story or task's "Labels" field updates. All actions are updated based on "Copy from Parent Issue"
Hello! I'm trying to get a label added to an epic to then add to the child stories AND remove a label from stories if removed from the epic. I'm able to get the label to copy from the epic to the child stories but cannot get the label to remove. Is this functionality now available or is there another rule I need to implement?
Hi @Mehgan Hawk -- Welcome to the Atlassian Community!
First thing: to get more people looking at your questions, please consider creating a new one and adding a link to related ones. Otherwise, often only the people already watching will see it.
For your automation rule, are you trying to keep the epic and child issues in synch on the Labels field, or could the children have more labels than are in the parent epic?
Thanks for the tip, I'll do that in the future.
As for this scenario...I'm trying to do a few things on on this topic.
1. have an epic with child stories, add a label on the epic and have the label appear in the stories
2. have an epic with child stories, remove the label from the epic which should remove the label from the stories.
3. have an epic with child stories, create a label on a story, add a label to the epic and see both the new epic label and the existing story label both on the story.
4. have an epic with child stories, create a label on a story, add a label to the epic and see both the new epic label and the existing story label both on the story. then remove the epic label and it should remove that label from the story but retain the story label.
After submitting my question yesterday, I've been able to accomplish 1 and 2 following the rules you've shared above BUT cannot get that rule to allow for 3 and 4.
Your scenario *can* work with 2-3 rules, and it has some risks to handle: such as an endless loop (runaway) in rule execution. The key is to have a stopping or "breaking" condition to prevent a problem.
You do not mention one thing: if the label changes in the Story, and cascades up to the Epic, do you expect that label change to cascade to the sibling stories also? Let's assume that is what you wanted.
Rule 1 would be checking for Epic changes and Rule 2 would be checking for Story changes. And, *neither* of these rules should have the option "Allow Rule Trigger" enabled in the details section.
Your rule was very close to what you need for Rule 1!
Here is an example for Rule 1, triggered on Epic changes, and cascading to the children. The idea is to use the changelog and delete the old labels before adding the new ones. This will require a re-fetch action, which slows down the rule quite a bit.
Rule 2 (Story up to Epic) is similar. I assumed you want the siblings in synch also.
There is possibly a Rule 3: cloned from Rule 2, but using a trigger of Issue Created when stories are added to the epic later.