Skip to main content

Background:

  • I have an automation that gets Assignees from an Assignee field and add them to a different Assignee Field

Problem: 

  • When there is more than one assignee in the first field, it seems to break and does nothing
  • It doesn’t seem to be able to handle the Assignee array / only single assignees

Example Use Case:

  • Using assignee fields like this with automations can help to centralize permissions in one place by team or other grouping (e.g. the “TEAM Members” database)
  • You can then allocate those assignments to cards in any other pipe.

Hi Keto,

This is not an expected behavior. 

Did you check if both fields are able to syncronize card's field with this fixed field and if all assignees are in all pipes involved?

Hi @julia-pinheiro 

Yes, I believe those criteria are met.

  1. Question: are you saying both fields need to have snychronize with assignee field checked on?
  2. More info: When the automation run it actually blanks out the assignee field. So if anyone was in it, it also clears them.

Hi!

  1. No, it’s not necessary.

  2. If the dynamic field of the automation is populated, it’s for the new field to be updated with the dynamic field information. If it’s not, the ideal is to check if there are any automation conflict.

    If the dynamic field is blank, both fields are expected to be empty.

Reply


Terms & ConditionsCookie settings