Create multiple issues with automation and give them assignees based on multi user picker

[Bent Möller]

I am currently trying generated a bunch of tickets based on a field "User(s)"

It starts with the following (which is working fine):

For each: Smart Value

Smart Value: {{issue.User(s).displayName}}

Variable Name: User

IF the component field contains Value A

THEN create a new issue with the SUMMARY "{{User}} please confirm the instruction."

So this automation is able to check how many users are in the User(s) field and then create an issue for every user and mention their name in the summary.

However, I want to also assign the issue to each person. But when I try to put the smart value from the branch {{User}} into the Assignee field, i will get an error "inactive user". This makes sense because the output "Person A, Person B" is indeed not a real user, but I don't know how to tell the automation to assign the first issue to the first person in the User(s) field, the second issue to the second person in the User(s) field and so on.

Is there a way to do this? I tried to change the smart value of the branch to {{issue.User(s).accountId}}, but that doesnt work either and then it will (obviously) show the account Id in the summary of the created issues instead of the name.

[Bent Möller · Accepted solution]

So, it looks like I found a way to do this.

When I create my branch, I dont use "{{issue.User(s).displayName}}" as a smart value, but instead "{{issue.User(s).AccountId}}". Then inside the branch where I create the ticket, I set "{{user}}" as the assignee. This way Jira has the correct ID to put it into the Assignee field end each created ticket has the correct assignee.

Only problem is now that, apparently, I cannot convert the Id back into a username to put the actuall name into the summary. Maybe this could work by adding another action after the ticket is created that then uses the assignee field to edit the summary, but this is actually not that important to me, so Ill go with it.

[John Funk]

Hi Brent,

You won't be able to update the Assignee field if the value is not a real user. I would suggest you use the user's email address for the value Users field, then it would work. Or update the Component to have the default assign it to a particular user for that component when a new work item is created. Be sure to add the Component to the new work that is created. 

[Bent Möller]

Hey John, thank you for your answer. Correct me if Im wrong, but I would say that a multi user picker is, in fact, a custom fields that provides the real user as I am able to take the user Id from it.

Doing this over the component lead does not work for me as this will be required for different users.

[John Funk]

Okay, I am confused then. You just said that you had a field called "user" but did not mention what type of field it was. Then you said:  This makes sense because the output "Person A, Person B" is indeed not a real user. So I assumed it was a text field. My apologies for that assumption. 

So if you are going from a multi-user picker field to a single user Assignee field, then that is probably your problem. The system doesn't know which user to to select, even if there is only one user in the field. 

Is that what is going on?

[Bent Möller]

Sorry for that, I only wrote it in the title that its based on a multi user picker. I did find a solution now though, see my other comment.