Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Automations

Showing 185 of 9748

Allow automations to update records created by the same automation

What is the challenge? Automations can be used to create new to-do, approvals, work-requests, and even requirements on features. It would be helpful to be able to populate certain fields on the newly created records at the same time that they are ...
Chris Quigley about 1 year ago in Automations 0 Future consideration

Trigger automations from an automated delivery risk flag

What is the challenge? When an automated delivery risk is flagged, I want to then enact an automation to trigger notifications and todos to key team members to address the risk. Today, automations only support the manual delivery risk flag. What i...
Max Robbins about 1 year ago in Automations 0 Future consideration

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 about 2 years ago in Automations 1 Future consideration

Automation to set a default estimate for all features created

I'd like the ability to set a default estimate for all features created. I checked the automation rules and the estimate field is not an option to update via automation rules. Some of our teams are doing a no estimates style of capacity planning w...
Guest almost 5 years ago in Automations 2 Future consideration

Automation to sync release dates with roll-up release

What is the challenge? Releases can have roll-up releases at the line level Roll-up releases automatically set their child release's release date However, there is no way to sync a release's date range fields to match the roll-up release What is t...
Nathaniel Collum about 1 year ago in Automations 0 Future consideration

Automation that pulls parent information when child field created

What is the challenge? Currently passing fields from parents to children (epic to feature or initiative to epic) can only be done when the parent is updated. This means when you create an epic under an initiative the fields are not automatically u...
Callum Hockey 12 months ago in Automations 1 Future consideration

Use AI agents and instructions in automations

What is the challenge? Automation rules in Aha! Roadmaps are currently limited to predefined triggers and actions. What is the impact? This restricts users from creating more adaptive and intelligent workflows. Describe your idea All...
Nathaniel Collum 6 months ago in Automations 0 Future consideration

Override Workspace Template Automations

What is the challenge? We have standard automations needed across a majority of the account with a few exceptions. We would like to disable those that we do not want to be used in certain workspaces. What is the impact? 99% of the time we want wor...
Michael Bruner about 1 year ago in Automations 0 Future consideration

Add Support for Workspace Rules in Automations

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 about 2 years ago in Automations 3 Future consideration

Allow updating child initiatives based on parent initiative fields in automations

Who would benefit? Those using roll-up initiatives to manage strategic work. What impact would it make? After updating a parent initiative, this would allow users to quickly have child initiatives update with relevant info without having to go thr...
Maria Plotkina almost 2 years ago in Automations 0 Future consideration