RELATED IDEAS
Automation rule that adds a new row to a custom table
In my use case we have a custom table on releases to track changes to the release date. I would like to set up an automation rule so that "when the release is updated and the date field changes to anything" then "add a row to the custom table with field 1 = x and field 2 = y, etc".
For this to really work well, we would also need to be able to copy the release date from the release to a field in the new row (idea A-I-9744).
This would be a huge help in tracking our data consistently.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +3
6
MERGED
Allow creating custom table records through automation actions
What is the challenge? Some advanced use-cases (such as tracking the history of a release assignment of a feature) are not possible today. What is the impact? This prevents users from tracking slipped work for work which has been re-assigned many ...
Likely to implement
© 2026 Aha! Labs Inc.•All rights reserved
For this to work really well, it would be great to be able to run an automation rule on update only (rather than create and update) - https://big.ideas.aha.io/ideas/A-I-13870.
For lots of requirements for effectively creating a targeted history table, the origin isn't as important as the change or even just the fact of the change.
Basically the functionality I am looking for is a history table, with the metrics from KPI, so that way, I can create a trending report over time. So when someone updates the KPI, the desired behavior was to create a new history record.
If not an automation, perhaps we could leverage the AI assistant to update a row on the custom table. My use case is for using the custom table as a change log.
I am tracking similar use case regarding slips/scope changes. We were hoping to add a new row to a table when a feature changes releases (with release name).