Add more specificity/granularity around automation logic.
Who would benefit? Both Aha! administrators and the product team members they support through administration of the tool. What impact would it make? It would allow Aha! administrators to automate actions and notifications that advancement can be m...
Christina D
almost 2 years ago
in Automations
1
Future consideration
Automation conditions based on related item fields
Who would benefit? All Users What impact would it make? We'd like to be able to create automations such as the following which is currently not possible: When an activity is created or updated and the related workspace changes (EG - the activity i...
David Willequer
almost 2 years ago
in Automations
1
Future consideration
Who would benefit? All users What impact would it make? We currently have custom fields at the workspace level and would like to be able to create automations based on when those fields are changed. For example: We have a custom user field "Progra...
David Willequer
almost 2 years ago
in Automations
2
Future consideration
Automation rules to update idea status when a comment comes in
I'm sure it never happens on your Ideas Portal, but often the Ideas that get submitted by our customers lack some key information that we need in order to make prioritization decisions. In those instances we put them in an "on hold or needs more i...
Derek Boriack
over 8 years ago
in Automations
3
Future consideration
What is the challenge? Set up automation rules for more than one workspace What is the impact? An easier way to setup automation rules in multiple workspace (without the need to copy the rules) Describe your idea Currently if we want to use the sa...
Edgar Holguin
11 months ago
in Automations
0
Already exists
Ability to add comment to related record via automation
What is the challenge?
We're updating related fields on related records via automation. We would like to be able to add comments to those related records indicating what happened and what the fields were updated.
What is the impact?
It mig...
Mat Buehler
4 months ago
in Automations
0
Future consideration
Extending fields available for Automation Triggers
What is the challenge? The number of fields available for use in the rule evaluation are limited. Therefore any automation to streamline processing of entries is restricted What is the impact? Many rules need to include a way of limiting the invoc...
Martin W
about 1 year ago
in Automations
3
Future consideration
Enable "copy" "move" and "Duplicate" automations in Workspace Templates
Who would benefit? Every admin updating the workspace templates. What impact would it make? Reduce the time to set up automations. How should it work? Same as the automation works in any workspace, you can duplicate a rule and move to other places.
Edgar Holguin
almost 2 years ago
in Automations
1
Future consideration
Update the Release associated with an Epic or Feature using Automation
We've integrated Aha! Roadmaps and Jira but the release information is not being synced. We can use automation to copy the Epic/Feature Release name to a custom PI field and use the integration to sync the custom PI field with Jira. But when the P...
Sandy Kobayashi
about 2 years ago
in Automations
0
Future consideration
Allow automations for custom tables based on another custom table
Who would benefit? Aha! users who have expanded their capabilities through multiple custom tables. Today, when custom tables reference each other, you need to update them on both sides. This drives no-value-add manual work and is ripe for inaccura...