Automations

What is the challenge? New conditional choice fields are not supported in automation rules. What is the impact? Unable to create rules based on choice field values. Describe your idea. Show choice field options when setting up automation rules.

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...

What is the challenge? Currently, it is not possible to clear an Epic's Initiative using automation rules. The automation rule only allows selecting a different Initiative (Screenshot 1) What is the impact? Inconsistent with Feature automation ru...

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...

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. ...

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...

What is the challenge? Creating and maintaining related links is a manual process. When a field on an epic is set or updated, the user must remember to navigate to its Related tab and manually add the corresponding link, which is time consuming an...

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...

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...

What is the challenge? There are two team members involved when we close a release and "Launch" ideas that are promoted to an epic in that release: one person that actually closes the releases and another that drafts and posts the admin responses....