I noticed a master release's initiative isn't inherited by attached releases and vice versa. There should be an option to enable this.

Categorical values, such as in a custom field with a pre-defined choice list, are by default sorted alphabetically in reports. However, in many instances there's a preferred or implicit ordering of categorical values. For example, the sequence "co...

I would like to be able to create comments on features, requirements, initiatives, etc. but have the option of those comments only being visible to myself. I will have discussion notes, code snips that relate to the feature/requirement but they ...

We would like a new setting in empathy sessions to prevent the historical chat from being displayed to users who join. This is because we conduct empathy sessions with customers of ours who are competitors so we don't want them in the session at t...

Currently when you produce an roadmap timeline report it has a vertical line representing today's date. It would be helpful to have the ability to add a line representing each release date on the roadmap.

Hi, I'm a big one for attaching documents to my projects. Some projects are starting to look a little messy now with the number of files attached. It would be good to be able to create folders to store the files in i.e. a folder for gate 1 and ano...

Looking for a reference document of all fields that are available in a default Aha setup. This document could then be used by admins to understand what fields are available, where they are (what tables; Releases, Products, etc) what the definition...

As a Product Owner, whose user stories are dependent on other user stories, features or ideas, I want to see the links between those other tickets so I can understand impact of other teams and can coordinate with other Product Owners to ensure the...

In our large organization, top-level Product Line owners should be able to add new, sub-Product Lines without needing Admin access. Admins have the power to change many global settings that could impact the work of others in the organization. I'd ...

1.0 did this; 2.0 does not. As a user I have to manually add the mapping between the URL field for an Aha! record and the Aha! Reference field for the JIRA record. For Releases we automatically map the URL to the description field. For Features/...