Application

What is the challenge? We have created a dashboard with report and text panels that we use as our product marketing one-pagers. We need to use this same format style across many workspaces, however, the text boxes can be individually updated but...

We have Improvement tickets in JIRA that we now (as new AHA users) want to migrate to ideas in JIRA. I have the JIRA integration created and would much prefer to import using the integration vs exporting tickets to CSV and then importing manually ...

By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...

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? Users are able to associate new features/epics to closed or cancelled initiatives What is the impact? Reporting on end dates for the parent is not reliable Describe your idea Force users to reopen parent OR select an alterna...

Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.

Who would benefit? Any user who is using the Now, Next, Later roadmap, or those who are creating their own version with a Pivot table. What impact would it make? It would allow users to more fully customize Now, Next, Later roadmap view to tailor ...

What is the challenge? We're expanding Aha!'s data model through the use of Custom Tables (Enterprise+) and are finding limitations in their support across the applications. What is the impact? We've enabled a Roles table on Epics and team...

What is the challenge? Currently there is limited support with using prototypes generated from the AI Assistant and adding them as files/assets to other Aha! documents and fields such as record descriptions What is the impact? Limited use ...

What is the challenge? Currently, you can create an AI prototype and add this to a record's description. The AI prototype is difficult to move around the record description if you need to reorder where it exists in context of other content in th...