Currently, if a user has set their epics or features to inherit dates from their children then when creating an epic or feature the due date is ignored and replaced with the date of the child records or is forced to be blank if no child records ex...

What is the challenge? The features board makes it possible to re-rank features by several fields. This view drives the details view order as well. We need this same capability for initiatives. What is the impact? We use initiatives prioritization...

What is the challenge? When publishing a knowledge base, some published notes designs may include the page's title. Currently, the title of the note is always displayed when displaying the note resulting in duplication. What is the impact? Duplica...

What is the challenge? searching for work allocated to your team currently not possible, only the assigned persons capacity team What is the impact? Means teams cannot easily create workflows or search boards for features where they have been allo...

What is the challenge? When prioritizing features using capacity per release, x-team capacity isn't taken into account by aha! What is the impact? Difficult to allocate features to releases where they may have varying team capacity requirements. D...

Allowing workflow approval groups to be used in a "to-do" approval will help streamline who is approving all epics without having to manually assign them every time. It will also allow us to continue using a flexible workflow.

It's ridiculous to have "paid seat groups" and allocate those licenses to other psg's within the account. Licenses limits should be observed strictly within each psg. I've lost seats for my group without my consent simply because they've over-allo...

I find this calculation the most accurate one and I want to place it in the highest hierarchy (company parent line) so that it can be inherited to all the workspaces in my account. Today, this option is available only in workspace level. Which mea...

Add Description fields as a filter option in reports. MVP options "is blank" "Is not blank" so we can find object records where the description is not filled in.

In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA. I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...