In the primary record you can only select one record type, and hence visualize only fields from that record. However, you can add filters on other record types. Would be more convenient to also be able to visualize and sort these in the primary re...

On this and many other screens the heading, which consists of the title, type of the view "Starter roadmap", switcher for "Milestones|Epics" and view control buttons, takes the hieight of at least 3 rows of content below (e.g. 3 epic bars). Having...

When you view a Custom Table, by default all the columns are shown. That makes viewing the table difficult, I would like a way to Add/Remove columns that are displayed for a Custom Table

YubiKey is a secure, hardware-based method of two-factor authentication. Please add support for 2FA via YubiKey to Aha!

Aha! sends out the "consolidated" to-do notifications in e-mails which is a nice functionality. However, as the number of to-dos increase from various goals, initiatives, releases the confusion increases as to which context these are related to. F...

Epics and Stories are two different constructs and should have separate release cadences. For us epics usually span for a quarter or more whereas stories are delivered within a biweekly sprint. My product team follows a unified quarterly planning ...

when we first used Aha; the release view used to have the gannt chart within the 'phases' tab... where since you applied new gannt charts you replaced it with a small 'view gantt' button; a pretty annoying extra click tbh as the gantt view that wa...

When adding other entities like scenarios to a feature, it is useful if we can associate a feature number rather than the feature name which is the default field when you use the many to many table

As a Product Manager, I want terms to be displayed a certain way so that it communicates my intent. Instead of "feature", I prefer the "PBI" and "Product Backlog Item". My terms, however, get as "Pbi" and "Product backlog item", respectively. I th...

We understand that the IDs in AHA and JIRA are meant to be treated as separate IDs without a true association between the two systems. However our workflow allows us to use the same IDs in both systems, assuming we enter them in the same order. Ho...