Hello,
We are using labels in JIRA board for various initiatives. We wanted to automate the population of labels based on the parent issue type's label value. Can you please let me know what trigger / JQL condition we can use. We have Initiatives, Features, Epics labelled and when we create a story, we need the labels to be auto populated.
Thanks in advance!!
Hello @Senthil V
Welcome to the Atlassian community.
When the Story is created, would it get the labels only from its parent Epic, or does it need to traverse the hierarchy to get all the labels for the Epic plus the Features, plus the Initiatives that are in its hierarchy?
An Automation Rule could populate the Labels field in the Story after the issue is created, but a rule cannot populate the field in the Create Issue dialog before the issue creation is completed.
Hello Trudy,
I would need the labels only from Epic. In future we may also need to get them from Feature to Epic to Story. It would be nice to have the automation rule for both scenarios. We do not need the label values from the Initiatives.
Thank You
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you want to copy the labels from the Epic only when the child issue is initially created? That would be one Automation Rule.
What if the labels on the Epic are changed at a later date? That would be another Automation Rule.
What if the child issue is moved to another Epic? That would be a third Automation Rule.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Senthil V
Have you made an effort to create these rules yourself with guidance from the documentation?
https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/
There is also a Templates tab in the Automation page. You might find example rules there that match your scenarios.
And at the bottom of the Templates tab is a link to an Atlassian site. You might find additional rule there.
It is valuable for you to learn how to construct rules. This will be a useful skill for you to have.
Do you want to copy the labels from the Epic only when the child issue is initially created? That would be one Automation Rule.
Trigger: Issue Created
Condition: Related Issues Condition
-- Parent exists
Action: Edit Issue
-- Field to edit: Labels
-- Value: Copy from Parent
What if the labels on the Epic are changed at a later date? That would be another Automation Rule.
Trigger: Field value changes for Labels
Condition: Related Issues
-- Children exist
For Each: Related Issue: Children
Action: Edit Issue
-- Field to edit: Labels
-- Value: Copy from Parent
What if the child issue is moved to another Epic? That would be a third Automation Rule.
Trigger: Field value changes for Parent
Condition: Related Issues
-- Parent exist
Action: Edit Issue
-- Field to edit: Labels
-- Value: Copy from Parent
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Trudy Claspill - Thank you sharing this automation rule. I was trying the Issue created in automation rules but couldn't get to "Copy from Parents" option. This is very helpful and saves lot of manual effort to in maintaining the reports/views. I really like this automation options available in JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.