RELATED IDEAS
Specify which fields will and will not be copied when copying a Feature
What is the challenge? |
When a Feature is copied, any field that is filled in will automatically be copied over to the newly created Feature |
What is the impact? |
Although most of time this is ok, some fields are Read-Only and therefore cannot be cleared without creating a list report and clearing the field that way. |
Describe your idea |
Either by an automation rule or some other method it would be useful to identify which field(s) to include or exclude when copying a Feature |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
© 2025 Aha! Labs Inc.•All rights reserved
We have several automations both within Aha and custom built against the API that populate fields for integrations with other systems. These fields are read-only as the data is coming from somewhere else or being calculated. We also need to be able to define which fields to include/exclude as part of copying a feature. Today copied features have incorrect information that the user can't clear. This causes a data integrity issue for us.
This logic should also apply to Releases and Initiatives!