Skip to Main Content
ADD A NEW IDEA

Features

Showing 1173 of 8826

Nest or group to-do items together

Who would benefit? PMs, Product Ops, docs team, What impact would it make? Easier to use and navigate to-do lists within discrete phases How should it work? I'd like to be able to nest or group to-do checklist items under a higher-level checklist ...
M K 6 months ago in Features 0 Future consideration

Teams can inherit delivery risk settings from the team line.

One can set delivery risk settings on the team line but these appear to have no effect. It would be nice to have teams be able to set their delivery risk settings to inherit from their team line, similar to how card customizations are intended to ...
Paul C about 1 year ago in Features 0 Future consideration

Allow feature boards to show releases and their features across multiple products

This would allow for an easy view that can be used to review and prioritize features, especially when features across multiple products have dependencies. Viewing and filtering multiple releases from different products in the same features board w...
Guest almost 5 years ago in Features 2 Future consideration

Add views to Aha! records

It's possible to Add Aha! view to notes. We need the ability to embed views into records. We are often referencing work (in lists and pivots) within our records but we have to manually type it out.
Nathaniel Collum 12 months ago in Features / Reports 1 Future consideration

Have workflow status change dates refelect the most recent date a status was set

The value of “Status changed to <status X>” for a feature workflow appears to perpetually contain the date of the first time that the status was changes to <status X> rather than the date of the most recent transition to <status X&g...
David Kettinger almost 8 years ago in Features 6 Future consideration

Rename product value field in non-product workspaces

The product value score terminology works well for workspaces where teams are building products. But in other workspaces it can be confusing. In these cases a more generic field name would be easier to understand.
Austin Merritt over 2 years ago in Features 1 Future consideration

Option to sort cards in reverse

Who would benefit? All Users What impact would it make? Save lots of time How should it work? If you have 30 releases already released like we have, you have to scroll multiple times to the right every time you open the page to get to the newest r...
Ryan V 6 months ago in Features 2 Already exists

Update workspace name/ID in record-reference-pill

As a product manager working with multiple workspaces, I would like the ability to change the workspace once a Feature has been created and have the new workspace name/ID update the displayed record-reference-pill copy/identifier automatically or ...
Elle W over 1 year ago in Features 2 Future consideration

Allow features to be grouped by epic in feature board and feature workflow

Currently, there is no grouping available in feature board. In feature workflow, it is possible to group by assignee. It would be great to be able to group both views by epic.
Joao Tornovsky almost 3 years ago in Features 0 Future consideration

Allow multiple workflows in a product

Within a given product there can be different types of initiatives and features. Aha! supports the concept of feature types and allows templating of the description field by type. Would like to see an expansion of this concept to support configura...
Bonnie Trei almost 5 years ago in Features 4 Future consideration