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
I would like to be able to create automation linked to "to do" or "approval" tasks. There's two use cases for us. First, I'd like to automatically change the status of a feature or epic once all to dos are completed or all approval replied in the ...
Dael Jackson
almost 5 years ago
in Automations
1
Future consideration
Automation rules to include custom fields from advanced custom layouts from a workspace
What is the challenge?
Currently, custom fields on advanced custom layouts aren't available on workspace or product line automation rules. Only custom fields from workspace layouts are available in automation rules
What is the impact?
Cann...
Terence Osmeña
3 months 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
11 months ago
in Automations
1
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 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
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
12 months ago
in Automations
0
Future consideration
Automation: Allow Automations for Release Phase and Release Phase To-Do objects
What is the challenge?
In order to track Release Checklists in Aha as to-dos by cross-functional team members needs automations to decrease amount of updates and auto assign appropriate owners.
What is the impact?
Cross-functional team mem...
Alex Berestenko
3 months ago
in Automations
0
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
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