Automations

What is the challenge? Custom layouts can be applied to to-dos and to-dos can be created from automation rules associated to records. When setting up a to-do none of the custom fields display for users to set. What is the impact? Users have to adj...

We have "Same as" functionality for certain field types now available for automations. It would be helpful to see the same ability extended for number fields, so related/promoted records can be populated with these when they are created or updated.

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

Who would benefit? Workspace admin & users What impact would it make? improve reliability and documentation How would it work? Allow the extraction of metadata detailing existing automations By providing an endpoint or similar option to output...

What is the challenge? For data quality, we want to notify an Epic/Feature creator when then have forgotten to tie the record to an Initiative, Objective, or Key Result What is the impact? Work that should be tied to these is not visible, monitore...

What is the challenge? Recently the ability to sync goals between epics and features was added to automations which is great! However, not all customers use epics, but still want a way for goals to be automatically synced to their lower level work...

What is the challenge? Trying to configure a release automation to set the "Feature start date" and "Feature due date" to be the same as the "Release start date" and "Release due date" What is the impact? Using custom/alternate fields where this i...

What is the challenge? Today, Themes cannot be automatically assigned to Ideas based on predefined logic (e.g., Category, tags, or other fields). This requires manual effort to link Ideas to strategic Themes, which is not scalable as our products ...

It would be great to be able to make an automation rule based on a date field being updated in a separate workspace. This would enable our teams to communicate more efficiently when work items are linked, without needing to update the same field i...

What is the challenge? Currently, Aha!’s automation only supports conditions on the trigger—not on the actions. This creates a need to duplicate automations for each variation, such as routing Epics to different Jira projects based on the assigned...