Automation set assignee in field multi-picket in parent task

Mario Quercia April 8, 2024

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?

1 answer

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 8, 2024

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 8, 2024

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events