Automation set assignee in field multi-picket in parent task

[Mario Quercia]

Hi, how are you?

I am having problems with an automation rule, in which I have 4 subtasks associated with a task. And I want all the assignees in the subtasks to go to a multi-picker type field in the task, but the automation deletes the assignee when passing them into the field. Can you help me what the rule should be?

-----------

Hola, como andan?

Estoy teniendo problemas con una regla de automation, en la cual, tengo 4 subtask asociadas a una task. Y quiero que todos los asignados en las subtask pasen a un campo de tipo multi-picker en la task, pero la automation me borra los assignee al pasarlos en el campo. Me ayudan como tendria que ser la regla?

[John Funk]

Hi Mario,

Can you share the rule with use here? 

Also, the Assignee field is not a multi-picker field. It is a single user field only. 

[Bill Sheboy]

Hi @Mario Quercia 

Adding to John's answer...

Assuming you are setting the users in a multiple-select user, custom field, you could gather the Assignee values from the subtasks and use them to set the parent Task's custom field using JSON, as described here:

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-user-picker-custom-field

Kind regards,
Bill