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

Rule for Copy and Remove Labels, to child issues

Rodrigo Baccaro Kazlauskas

Hey everyone, im trying to create a rule for copy and remove labels to child issues.

Then any changes to the labels must be copied to child issues.

Would anyone have an example?

Accepted answers

Bill Sheboy

Hi @Rodrigo Baccaro Kazlauskas

Would you please clarify your use case? Do you want to

keep the parents and child issues in synch (same exact labels), or
child issues can have more labels than the parent and include all parent labels?

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Rodrigo Baccaro Kazlauskas

Would you please clarify your use case? Do you want to

keep the parents and child issues in synch (same exact labels), or
child issues can have more labels than the parent and include all parent labels?

Kind regards,
Bill

Rodrigo Baccaro Kazlauskas

Hi @Bill Sheboy

Thakns for your reply.

I didnt think about the option 2, but this option will be better. Could you help me how to setup this 2nd option?

King regards

Bill Sheboy

This is the more complicated option, as you first must remove the previous labels the parent used, and then add the current values. Both of these use the {{changelog}} smart value.

For example, this rule would be triggered on a parent epic's labels changing:

trigger: Value changes for Labels
condition: issue type is Epic
branch: for stories (or other issues) in the Epic
- action: edit issue Labels (to remove old values)
  - Values to add: leave this empty
  - Values to remove: {{#changelog.labels}}{{fromString.split(" ")}}{{/}}
- action: re-fetch issue to reload it after the changes
- action: edit issue Labels again (to add)
  - Values to add: {{#changelog.labels}}{{toString.split(" ")}}{{/}}
  - Values to remove: leave this empty

This one grabs the prior values (fromString) for the triggering epic, and splits them up so they can be removed from the child issue. Similarly the new values (toString) are then added. I believe this must be done in separate steps, with the Re-fetch in the middle, to avoid a collision.

I recommend trying this in either a test project or with test issues first. If it does not work as you want, you can switch to Case 1 (simple replacement), as that is much simpler.

Rodrigo Baccaro Kazlauskas

Hey @BIL

I've tried this setup, but is not working. There is something wrong how i built it?

Jira automation label.jpg

Grace Shaw

***Assuming the child issues will always have the same labels as the parent:

1. Create the Trigger: "Field value changed" (Labels)

2. Create a "Branch rule / related issues":

Set "Type of related issues" to "JQL"
Use the following JQL filter:

issuekey in portfolioChildIssuesOf{{issue.key}}

3. Create an "Edit issues" action

Select "Labels" from the "Choose fields to set..." dropdown
In the Labels field, select "Copy from parent"

If the child issues may have different labels than the parent, then you will have to parse the changelog.

Bill Sheboy

Hi @Grace Shaw -- Welcome to the Atlassian Community!

My understanding is the function portfolioChildIssueOf() is only available with Advanced Roadmaps, provided with a Premium Jira license. And the person who originally asked this question is not on that license level.

Kind regards,
Bill

Grace Shaw

@Bill Sheboy — I did not realize these details (that portfolioChildIssueOf is an Advanced Roadmaps-only feature, and the user's license level). Your answer is more robust anyway. Thanks for the feedback!

Adam Ziecik_0l2wrj

*deleted*

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

jira-software-cloud

atl-gruland