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

Based on multi select field values clone issues to other projects, more than one at a time

Javanshir Mustafayev_bdjtbc

I have a multi select field with values equal to the list of projects (7 out of 30 projects currently in my Jira Cloud).

When I select single value for this field my automation clones the epic where needed.

The problem is that when I select more than one values only one project gets the issue cloned, the rest are ignored.

How do I make it work?

Is this happening bcz I use else-if in the automation? I can't get more than two IF's without having the else-if appearing as the third option, and I need 7.

I need this to work from a single automation, as I'm allowing my users to trigger it manually when they need it. It isn't an option to create multiple rules that would do this.

Any help is appreciated.

Accepted answers

Javanshir Mustafayev_bdjtbc

Solved by changing the else/if to else.

The rule was stopping when reaching any of else/if successfully. After changing all conditions to else only - works as expected for any number of values for the multi-value field.

All comments

Peter_DevSamurai

You might want to look into the "Advanced branch rule / related issues" component in Jira automation to handle multiple projects. This component allows you to branch your rule and perform actions based on related issues or fields like your multi-select field.

John Funk

Hi Javanshir,

Can you share the rule that you have so far please?

Also, if you use If/else, the rule will stop when you meet the condition the first time. That’s probably what you are seeing.

Add a branch for Current Issue for each project, along with the appropriate condition under each branch (you can just use the issue fields condition).

Then add your Clone issue under that. Once you do the first set, you can copy the branch and just change out the project in the condition.

Javanshir Mustafayev_bdjtbc

Solved by changing the else/if to else.

The rule was stopping when reaching any of else/if successfully. After changing all conditions to else only - works as expected for any number of values for the multi-value field.

Bill Sheboy

Hi @Javanshir Mustafayev

As others have described, the advanced branch on smart values will help in this situation.

Specifically, you could use the additional smart values around field changes: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--

These would allow both adding the new values, and deciding what to do if a value was unselected from the list.

Kind regards,
Bill

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