When working with high level initiatives that span many quarters, current view demands lot of scrolling (using Quarter resolution). The quarter scale shoud be compresses to allow the full span view in a single page ideally.

A button, when pushed, would recompute the work done and work remaining in a release, based on the current status of feature or requirements within the release. Presently, Aha's computation of work done is automatic and event-based, i.e., It happe...

When we create a new feature we populate the box labelled description which is mapped to description in JIRA - the user story. . But in the detailed view in AHA! that description text appears in a blank box. Are we able to label this description?

This would be beneficial for those who create large presentation reports from other pages in the Aha program. It is cumbersome to check each individual slide to ensure that the Update Frequency is set correctly or change it if necessary and it wou...

I want to use one set of terminology at the Product Line level and another set within its Products. ie, Initiatives at the Product Line level and Epics at the Product level. Allow me to set the terminology for all products in a product line's conf...

Who would benefit? anyone making a chart What impact would it make? better ux How should it work? when i select a top level parent category checkbox to filter by, and it has children paramters, they should all get checked too. Also, when I save ch...

Background: There are cases where a contact represents multiple organizations and we want that person's feedback to count as feedback for each of those organizations. The challenge: If they are using a generic email address, like gmail, it does no...

Could you expand Zapier or Power Automate to support more scenarios? Currently using Aha makes many areas like user admin 100% manual, which seems so 1990's. Any chance of supporting more so we can do more with Automation?

The issue was discussed with Aha Support under https://support.aha.io/hc/requests/357023 Useful to consumers of Release-related reports at all levels (including C-Suite). Problem: We name all of our releases with just the release number (e.g. 2019...

Editing permissions are currently based on memberships in a product, there is no option to control them by individual users. In a situation when we have a critical report that we do not want everyone that is part of a product to edit, the only oth...