RELATED IDEAS
Support "same as" automations for choice lists
What is the challenge? |
Automations currently make it possible to pass values from one record to another, such as users and dates. We need the ability to set the same choice lists across records. |
What is the impact? |
We often plan our work by component where we set choice lists for different parts of the platform. When an initiative is created, it's in support of specific platform component. Any features created in that initiative should have the same platform component. Not having this forces our PMs to have to remember to update that field. |
Describe your idea |
Support "same as" automations for choice lists |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +3
© 2026 Aha! Labs Inc.•All rights reserved
We also require this for our processes. We have a field Yes/No to determine if an Initiative, Epic or Feature should belong to a specific process. The intention is to automatically determine this by hierarchy: if the Epic belongs to an Initiative that has Yes, then the Epic and its Features should along be Yes too.
At this moment we can make this happen when the records already exist and a change is made. However, when for example a Feature is newly created and the Epic's field is not changed, then the field is not updated.
For this scenario we require that upon creation of the Feature the automation rule could retrieve (MATCH) the Epic's value for the field.
This would be a game changer for automations, and I'm actually surprised that it's not there.