Allow for automations that "match" multi-select fields
What is the challenge? We need to be able to automatically populate multi-select fields in lower-level item types based on the entries in top-level Ideas. Today we have to create individual automation rules to add and remove each individual list s...
Guest
10 months ago
in Automations
0
Future consideration
What is the challenge? We have automations that push fields downstream to other item types. Since they can only be triggered when the top-level item is created or the field is edited, the automations are not pushing data to the lower levels becaus...
Guest
10 months ago
in Automations
0
Future consideration
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 tags across records. What is the impact? We often capture a key customer's name o...
Nathaniel Collum
about 1 year ago
in Automations
0
Future consideration
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
5 months ago
in Automations
0
Future consideration
Automation rules should be able to update a related goal's status
When creating an automation rule it is not currently possible to update a related goal's status. Goals are the only related record type for which you cannot update the status. In my example, I would like to update the goal status based on a change...
Kelly Sebes
over 5 years ago
in Automations
2
Future consideration
Automation Rules are incredibly powerful but are limited to a very small subset of standard fields per item (ideas, epics, features, initiatives, etc.). We're constantly finding ourselves wish that a standard field would exist so that we can creat...
Conner Helton
over 2 years ago
in Automations
1
Future consideration
Allow automations to create calculated fields like reports
In reports one can create columns that are functions of other columns... this allow one to construct properties based on other variables assocaited with the object.For example I'd realy like to be able to set another custom variable based on the p...
Nigel Lawrence
almost 4 years ago
in Automations
0
Future consideration
I have a mandatory custom field in Aha! Feature’s form and I would like the field to be non-editable once the release is approved through fixed workflow statuses, so that people could not make any changes there and any exception changes should go ...
Ankush Kumar
over 2 years ago
in Automations
1
Future consideration
Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
Guest
about 3 years ago
in Automations
0
Future consideration