What is the challenge? Currently, it's not possible to customize a delivery risk rule by a record's status.
What is the impact? Records are flagged with delivery risks at a time in the status workflow, when those risks are not relevant.
Describe...
Ben Hollier
3 days ago
in Automations
0
Future consideration
Ability to ignore weekends for the duration calculation in the automation rules
What is the challenge? We want to exclude weekends during the automation rule calculation involving days.
What is the impact? Impact on the SLA for ideas that gets submitted and actioned.
Describe your idea. The scenario is when an idea gets sub...
Support custom fields for Approval and To-do automation actions
What is the challenge? Currently, it's not possible to set custom fields on an Approval, when one is created via an automation rule.
What is the impact? Important information is not visible directly on the Approval. Approvers must navigate to the...
Ben Hollier
4 days ago
in Automations
0
Future consideration
Update an existing Release with information from a Template without impacting progress
What is the challenge?
Need to update existing releases with language that was refreshed in a Template.
What is the impact?
We use 10 different Templates and have about 100 Releases in progress, which makes the copy-paste troublesome.
...
Diana Kuepper
about 1 month ago
in Automations
1
Future consideration
Automation support to sync promoted record's release to custom release field on source idea
What is the challenge?
Currently, it's not possible to create an automation rule that syncs a promoted record's release name to a custom release field on the source idea.
While it is now possible to sync to a custom text field, the custom relea...
Ben Hollier
about 1 month ago
in Automations
0
Likely to implement
What is the challenge?
In it's current state triggers for automations if you want to add multiple conditions only support "and", you can't do multiple "or" triggers.
What is the impact?
This requires you to make one automation to every one...
Erik Baerresen
26 days ago
in Automations
0
Future consideration
Add support for aggregate logic in automations (e.g., parent status based on all child record statuses)
What is the challenge?
Aha! currently supports automations that trigger when a single child record changes state (e.g., “If an epic becomes At Risk → mark the parent initiative At Risk”). However, Aha! cannot support the inverse logic — resettin...
Guest
about 2 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 text fields across records.
What is the impact?
We often plan our work b...
Terence Osmeña
7 months ago
in Automations
0
Future consideration
What is the challenge?
Automation workflow does not currently have the option to update theme based on idea criteria
What is the impact?
Cannot automate setting of theme based on an idea category
Can only be manually set
Describe your ...
Suzanne Pritchard
16 days ago
in Automations
0
Future consideration
What is the challenge?
There are actions that need to be taken when a date field is populated (regardless of the date selected.) The trigger can only be 'is blank' or 'is exactly, later than, earlier than, anything'[select date]
What is the ...
Guest
3 months ago
in Automations
0
Future consideration