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

How to set the assignee to the current value of the multiple choices field

vincenzo.spatafora

Dear ALL,

who can help me out?

I have created an automation rule which triggers upon issue transitioned and the action is simply to update the assignee field with the current value of a multiple choices field (select list) called in my case Responsible.

This rule runs with NO error, indeed, the log reports “Issues edited successfully” BUT nothing has happened actually, I mean, the assignee has NOT changed as I wanted.

This is my syntax:

{

"fields": {

"assignee": { "name": "{{issue.Responsible.name}}" }

}

I use Jira DC version 9.12.12.

Thanks in advance, Vincenzo.

Accepted answers

All comments

Radek Dostál

So you have a multi select, but you're using a json path to a single value. Of course that won't and shouldn't work.

If it's "multiple choices field (select list)" I would imagine it's an option based field, but I hope it really is a multi user picker?

How do you choose which user to pick from the list and how do you handle a scenario where the list is empty?

Consider logging the value you're getting from "{{issue.Responsible.name}}" to see what you're getting.

After that I assume you will need to get a single value from the list like this https://confluence.atlassian.com/automation/jira-smart-values-lists-993924868.html

John Funk

Hi Vencenzo,

Jira doesn't know which value of a multiple value field to get to put in a single assignee. You can do this to get the first value in the multi-field though.

In the box for the Assignee field, put this:

vincenzo.spatafora

Hi John,

I have tried that out:

no errors but the assignee has not changed and from the log the smart value of {{issue.Responsible.get(0).accountId}} is empty, it's empty also for {{issue.Responsible.get(1).accountId}}.

Thanks, Vincenzo.

John Funk

Let's try this then: {{issue.Responsible.get(0)}}

vincenzo.spatafora

@Radek Dostál,

yes, it's a multi user picker whose value it's already set within the Jira ticket (for example to me).

NO scenario at all where the list is empty because at the time of creating the ticket I set this field (Responsible) to one of my team member.

The log of {{issue.Responsible.name} is empty actually but then I have logged {{issue.Responsible.value} and the value is the current user (for example myself).

So, I have used the following syntax:

{

"fields": {

"assignee": { "name": "{{issue.Responsible.value}}" }

}

And now you get this error message:

Error editing issues

GAL-5919 (User 'Spatafora, Vincenzo' does not exist. (assignee))

Thanks for letting me know,

Vincenzo.

Radek Dostál

Well, just do issue.Responsible.get(0).name as you did - the only difference is the getter by index.

Or issue.Responsible.first.name to make it more "readable".

It does surprise me that it would be empty in your original format though. Purely json-syntax wise it is not a valid getter, but A4J documentation makes it seem that it should return the array of names. Meh, either way.. first.name should work.