Who would benefit? Customers with a lot of workspaces and workspace lines What impact would it make? This would make it easier to see more content on this page at once and more easily adjust the hierarchy and edit workspaces. How should it work? T...

Once a month I go through a couple of days where Aha tells me I'm not logged in EVERY time I take an action. I log back in and search for something and get the snack bar that I'm logged out again. When I log back in, it takes me to my features pag...

Use case: Organizations are used to track customer information. We have created a record relationship custom field (type: organizations) on epics and features to specify customers the work will impact. Challenge: When building list/pivot/chart/cus...

Who would benefit? Customers integrating Aha! with other systems e.g. Jira Customers with specific audit/traceability needs What impact would it make? It would allow record history to most accurately depict what led to a change How should it work?...

When connecting a ticket to an idea via the ZenDesk integration, sometimes you receive an error. This could be because: The user who authenticated the integration created the idea so has already voted The user who authenticated the integration no ...

Currently, the search results may list multiple instances of the same item (i.e. feature) on the search details page. This occurs when searching for text and that text is included in multiple fields on the item. As an example, "allergies" is enter...

The filter for release name in the features roadmap should default to show all releases. Currently if you click "Clear selected items" it shows no releases. This make it cumbersome to try to get all releases shown and then apply appropriate filter...

In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...

We would like to be able to 'lock down' some fields unless there is approval to change them. For example, Release date (or due date) Budget Designated people in the company would be required to approve any changes to these fields. Along with this,...

Problem We use filters a lot, but they are super clunky, requiring multiple clicks to change the filter, and with some Internet latency b/w the clicks the UX suffers even more. This slows us (me) down. Combining of the filter field selection with ...