Automations

What is the challenge? Need to update existing releases with language that was refreshed in a Template. What is the impact? We use 10 different Templates and have about 100 Releases in progress, which makes the copy-paste troublesome. ...

What is the challenge? In it's current state triggers for automations if you want to add multiple conditions only support "and", you can't do multiple "or" triggers. What is the impact? This requires you to make one automation to every one...

What is the challenge? Currently, it's not possible to create an automation rule that syncs a promoted record's release name to a custom release field on the source idea. While it is now possible to sync to a custom text field, the custom relea...

What is the challenge? Aha! currently supports automations that trigger when a single child record changes state (e.g., “If an epic becomes At Risk → mark the parent initiative At Risk”). However, Aha! cannot support the inverse logic — resettin...

What is the challenge? Automation workflow does not currently have the option to update theme based on idea criteria What is the impact? Cannot automate setting of theme based on an idea category Can only be manually set Describe your ...

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 text fields across records. What is the impact? We often plan our work b...

What is the challenge? We would like improvements to Aha! automation to make it more scalable and efficient across workspaces. 1. Bulk Automation Management Allow bulk select and move/copy of automation rules across workspaces to reduce manual ...

What is the challenge? There are actions that need to be taken when a date field is populated (regardless of the date selected.) The trigger can only be 'is blank' or 'is exactly, later than, earlier than, anything'[select date] What is the ...

We have "Same as" functionality for certain field types now available for automations. It would be helpful to see the same ability extended for number fields, so related/promoted records can be populated with these when they are created or updated.

What is the challenge? When adopting custom tables in Aha! we are able to create automations but are unable to create to-dos as an Action. This is likely due to the decision to not include to-dos on custom tables. https://big.ideas.aha.io/ideas/...