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

Inherit multi-select field from hierarchy parent using automation

Julia Foden

In a hierarchy which has Milestone and Feature levels above Epic, I need to make Features inherit a multi-select field from their parent Milestone when they are created.

In testing I have created a rule that works for a single select field, as described in my answer to this question. But how to make it work for a multi-select field? The variable contains a comma-separated list. How can I manipulate that so that each value is added to the field on the created Feature?

Can I split the comma separated list into a new smart value that can be branched on?

Any other suggestions welcome, if there is a better way of going about this.

Thanks

Accepted answers

Bill Sheboy

Hi @Julia Foden

Without seeing your rule, I suggest the answer is "maybe". Please take a look at advanced branching for options to iterate over the values from a list. (You may use list functions and the CSV values you note to drive the branching.)

https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Julia Foden

https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935

Kind regards,
Bill

Julia Foden

Hi @Bill Sheboy

This is what I have

Screenshot 2021-11-04 175446.png

Strategic Initiative is a multi select field and the log output is a comma separated list. If there is just one value it edits the field on the trigger issue correctly.

I tried branching over the variable {{SI}}

Screenshot 2021-11-04 175938.png

and then using this to update the field

Screenshot 2021-11-04 180000.png

but the error was

(Option value 'ABC, XYZ' is not valid (customfield_16576))

Is it possible to manipulate my variable {{SI}} (comma separated list) in such a way that Advanced Branching recognises it as a list that can be branched over?

Thanks for your help.

Bill Sheboy

Yes, now that you have confirmed that {{SI}} contains a comma-separated values (CSV) list of the data you want, change the Advanced Branch to use:

{{SI.split(",")}}

That will convert it into a list which is then input to the branch.

Julia Foden

Ah thanks @Bill Sheboy , that's the final hurdle!

What a palaver though, to copy one field from the parent. Do you happen to know if there is a feature request in to enable copying a field from the hierarchy parent, in the same way that we can from the Epic, trigger issue etc?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation