I recently discovered that subtasks created by rules do not inherit values for private custom fields or public custom fields with Guest set to “no access.”
In our situation, some of those subtasks are multi-homed into other projects for further action by other teams or for reference by a wider group. I was hoping to use private custom fields to help tailor the information visible to members of the reference project who need to know and simplifying the view for members who only need higher level data.
I ran into this today, which led me to this forum post. I made an existing field private. It was only used to drive backend automations and I wished to simply hide it from cluttering the views of others. In our scenario, we’re seeing both:
- Tasks created by rules no longer inherit private custom field from parent task
- Tasks created by rules no longer gain the specific private custom field selected within the rule
No alert was provided in the rule that anything was broken and needed to be fixed.
We made a handful of fields private on Friday and discovered on Monday the functionality around this was not working as expected. We’ve rolled back the field visibility to stop disrupting our workflow until we can create a workaround or hear this will be addressed by Asana.
1 Like