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

Aggregate field values from all Epics under an Initiative

Shir Avtabi

Hi all,

I'm trying to find a way to create an automation that’ll inherit "Domain" field values from all Epics to their parent Initiative everytime the field values are updated or when the parent is changed.

I found a way to make it happen but there's an issue if the Initiative has 2 Epics or more under it: The values in the Initiative will stay as they are and the automation just adds the new values to it - But keeps the old values as well which are no longer relevant:

domain auto old 3.png

To solve this I tried to first clear the Initiative "Domain" values (every time the Epic's "Domain" field is changed) and re-fetch the values again - But then it only takes the values from the Epic that was modified (the trigger issue), so it's not working for me.

Another idea was to use a variable or lookupissues to get a list of all the Epics under the Initiative - capture the values of "Domain" from all of them - and then put them back in the Initiative. When I tried that I got the following error:

(Specify the value for Domain in an array (Domain))

Any idea how to get past this error?

here's what I tried:

Domain auto.png Domain auto 2.png Domain auto - error.png

Accepted answers

Stevan Mandić

Instead of using "fields" (value:), try using: "update" (set:)

"update": {
"Domain": {
"set":

Take a look at the difference between "update" and "fields":
here

All comments

Stevan Mandić

Instead of using "fields" (value:), try using: "update" (set:)

"update": {
"Domain": {
"set":

Take a look at the difference between "update" and "fields":
here

Shir Avtabi

Hi @Stevan Mandić , thanks for your reply.

the goal here is to aggregate all the Epic's field values to the Initiative parent which means I'll have to clear the Initiative field first, so in this case "update" or "set" doesn't matter. Otherwise, it may keep the values that are no longer in another Epic's field.

I believe the issue is more related to the format expected by the field that differs from the one I get with the lookupissue.

domain auto 5.png

Stevan Mandić

maybe this can help:
https://community.atlassian.com/t5/Jira-questions/Parent-Inheritance-of-Child-Tickets-Multi-Field-Values/qaq-p/2659291

Stevan Mandić

@Shir Avtabi here is the working solution, just replace XXXXX with your Domain Field ID (both in variable and edit action)

this rule will always keep Initiative Domain field values updated when child Domains change.

1)Trigger: Field value changed (Domain)

2)Condition - issuetype equals Epic

3) Lookup issues - JQL:

issuekey in portfolioChildIssuesOf("{{issue.Parent}}") and issuetype = Epic

4) Create variable - "childDomains":

{{lookupIssues.customfield_XXXXX.value}}

5) Branch For: Parent

5.1) Edit issue fields - More options:

{
    "fields": {
        "customfield_XXXXX": [ {{#childDomains.remove("[").remove("]").split(",").trim}}{ "value": "{{.}}" }{{^last}},{{/}}{{/}} ] 
    }
}

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