Search results: Application

What is the challenge? Currently, automatic workflow syncing between records only works with the built-in status categories. Teams that create custom status categories to better reflect their workflow stages cannot leverage automatic status sync...

What is the challenge? Aha! Pages (Notes) provide a Status field in the UI, but this field is not available through the API. Because of this, teams cannot automate publishing workflows for documentation, release notes, or knowledge base pages. A...

What is the challenge? Aha! Pages include workflow fields like Status and Revision Status, but these fields cannot be updated through the API. This prevents teams from automating documentation and knowledge base workflows. What is the impa...

Who would benefit? Administrators and Product Managers What impact would it make? Reduce the number of automations for Administrators to maintain and manual steps for Product Managers How should it work? Add a configuration option to map Idea stat...

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

Currently, an Idea status will automatically update when it's promoted to a Feature and when the Feature is released. We would like another automatic update in between these, when the Feature is committed (we have a "Committed" status in our Featu...

For almost all our workflows, a parent record's status is dictated or a reflection of it's child record's status - similar to how the progress of a parent record is an aggregate of it's child records and that functionality. I would like the abilit...

We have a workflow where newly created ideas are submitted in a 'New' status. If the idea is unclear we update the statis to 'Need More Information" and we expect the submitter to provide additional information through public comments on the idea ...

I really love the simplicity of automation and would really like to make use of the feature much more. One thing that is leaving me hesitant is having to manually add in individual user names to send emails or add a to-do or approval. Sure, you ca...

Like you can do with To-dos, you can assign automation items based on user fields, i.e. assigned to and custom user fields like BA, UX, Developer, etc. We would like to be able to do the same with automation emails so that these can be targeted to...