Features

We want to add a dependency type to show that a dependency is no longer needed. Unfortunately, we sometimes create dependencies on other product Roadmaps but then are unable to contact the owner to remove the dependency. As a solution, we though...

Currently the "features" and "master features" relate to work output, not actual product concepts that users care about. tl;dr; please give us more ways to separate concepts from the actual work. Features should technically be conceptual, and shou...

As a Product Manager, I want the ability to clear or delete field values in bulk so that I can easily clean up errors in my data and ensure that Aha! is the definitive source of truth.

Other great Kanban-style boards (e.g., Trello, GitHub Projects) allow scrolling the individual columns which makes moving an item from one long list to a specific position in another long list much easier. I'd like to see this on the Feature board...

Problem Statement: The current permissions/licensing structure of Aha is cost prohibitive for companies with larger business review teams who need update feature descriptions prior to development (i.e. moving features through stage-gate prior to a...

I've commented on a requirement; until I click on the requirement, there's no indication that there's additional information to be seen. On Features' Board and Details views each feature card has a comment counter, but it doesn't reflect comments ...

Maybe a feature is created from an initiative that has a big BRD document attached. Instead of attaching the file again (thus duplicating it in the Files section) we could search and attach previous loaded files (as a pointer to that file).

Overview Let users set a default configuration for Feature Cards and apply that layout across all products they are members of. Background I love the fact you can customise the layout of Feature cards to include exactly what you want them to show....

I'm glad to see the dependency map feature appear. However, I notice it doesn't just show dependencies, it also shows "relates to" relationships. On the map, they are indistinguishable, which is confusing. It would be great if I could limit the ty...

In our development projects, features are often owned/assigned to more than one individual. Per intended use of the To Do's, we prefer to assignee the true list of owners to each feature versus creation of a To Do or use of the Program Manager fie...