Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,455
Community Members
 
Community Events
185
Community Groups

How can I iterate through a multi-select field in an Automation for Jira flow?

Edited

Hi

 

I have a multi-select field called "Teams". When the issue reaches the "Ready for Dev" stage, I want to create a subtask for each option selected in "Teams", populating a single select "Team" field in the sub-task.

 

Is there a way to iterate through the selected items in the "Teams" field, and run a branch for each selection? I'd also need a custom value to set the single-select Team field to, like {{multiselect.iteration}}.

 

Thanks

1 answer

Hi @stringsonfire,

There is a way that I found, but I'm not sure this is the easiest.

When the status = "ready for dev" run:

if "Teams" not empty -> "create issue" and populate the "Team" field with the smart value {{issue.Teams.first.name}}

on the more options, add the following:

{
"update": {
"Teams": [
{
"remove": {
"name":"{{issue.fields.teams.first.name}}"
}
}
]
}
}

You can use "re-fetch issue data" and continue the rule if there are more "Teams".

The other option is to change a different field so it will run a different automation rule as long as "Teams" is not empty.

If you don't want to lose the "Teams" field content - you'll need to first copy it into a different field.

Hi @Elad Ben-Noam

Similar to the case above, I have a scenario where I want to create issues on a particular transition. Here instead of Teams i have a multi-user field as "Stakeholders", and for each stakeholder added in this field, I want to create that many number of issues. Till here everything works fine.

The issue is that additionally I also want to set the "Assignee" of each newly created issue to each value in the field "Stakeholder". 

I tried this:

Screenshot 2021-10-27 at 14.20.57.pngScreenshot 2021-10-27 at 14.22.02.png

However, seems that I am missing something.

Could you please help :)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events