Automations
Sort by:
Trending
Filter by:
Status
Showing 179 of 9697
48
VOTE
Automation to set standard fields the same as custom fields when idea is promoted
We have a custom field for goals in the Idea ticket (where the requester must select which strategic goal their request ties to), but we can't map this field to the Goals field at the Feature level because they are both not custom fields. We have ...
5
Future consideration
4
VOTE
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...
0
Future consideration
5
VOTE
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...
0
Future consideration
22
VOTE
Add automations for to-do and approvals
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 ...
1
Future consideration
1
VOTE
Explicitly set order of priority for automations.
What is the challenge?
Automations on the same record type execute in arbitrary order.
What is the impact?
Out-of-order execution may lead to unexpected behavior.
Describe your idea
Give automation a priority system so it can be exec...
0
Future consideration
21
VOTE
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...
2
Future consideration
4
VOTE
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 ...
0
Future consideration
7
VOTE
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...
0
Future consideration
2
VOTE
Automation trigger for overdue releases
What is the challenge? The challenge is, we have many products and many releases. We track internal and external release dates but spend a lot of time chasing up PMs to either change their release status or release dates if the dates have slipped ...
0
Future consideration
11
VOTE
Automation Rule - Add "Release" as an Action
In my scenario, there are times that a feature is in a given status, and as a result, I would want that feature to move to a different release. For example, If I abandon a feature, I want it removed from a release and put into a parking lot where ...
2
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved