Automation Rule - Setting assignee for a subtask from a multi-user picker field from the parent

[Jeremy Davis]

I have an automation rule in place that will create a sub-task (called Validation task) based on the validators field (muliti-user picker custom field).

So it creates 2 subtasks if there are 2 validators.  Question is - how do I get the assignee set for each one of the subtasks?  I've tried using Assign Issue and specifying the user as {{issue.parent.key}} {{issue.validators}}  - this just throws an error Specified user does not exist or you do not have required permissions)

Tried testing this with just one validator (myself) and still fails.

Here's what the rule looks like.  As I said, it's creating the tasks just fine.

I did try changing the the smart value and put in {{issue.validators}} and I didn't get an error this time but see this in the audit log.

Assign issue

Issue was already unassigne

[Ntamen kamogne harry Michel]

hi @Jeremy Davis 

Normally the create ticket action can also assign values ​​to the fields of the new ticket created so no additional action is needed. and in addition, you can copy the value of the rule trigger ticket

when you add the create subtask action, there is the add fields option which allows you to fill in certain fields of the subtask automatically during its creation

Make sure that the jira automation user has the "assign issue" permission (normally by default he already has it)

[Ntamen kamogne harry Michel]

sorry for this misunderstanding

it's the smartvalue that is not the right one.

It’s definitely a custmfield, isn’t it???

in this case the smartvalu is as follows
{{issue.customfield_Idcustomfield}}

[Bill Sheboy]

Hi @Jeremy Davis 

From which field are you getting the assignee to use for the created issues?

If it is the same one as used in your advanced branch, that smart value expression could be set to the assignee field when the issue create action is used.

If it is a different field from the advanced branch, what you describe is not possible and would not make sense: issues can have one assignee and so the value from a multiple select field could not be used.

Kind regards,
Bill

[Jeremy Davis]

I agree with this but was hoping for a way to do this since it's branching and kind of looping already since it creates two sub-tasks based on two validators.  Looking at how to script this to loop through and create as needed.

[Jeremy Davis]

I am able to assign the issues from this automation to a normal thing like grabbing from the Assignee original ticket.

I am trying to set the assignee based on a different custom field that is a multi user picker field. 

Thanks for the info but it doesn't quite fit the scenario above

[Ntamen kamogne harry Michel]

désolé pour ce malentendu

c'est la valeur intelligente qui n'est pas la bonne.

C'est définitivement un domaine personnalisé, n'est-ce pas ???

dans ce cas, la valeur intelligente est la suivante
{{issue.customfield_Idcustomfield}}