Skip to Main Content
ADD A NEW IDEA

My ideas: Application

Showing 957

Paid Seat Transparency Across Aha! API

When calling get-all-users in the API we receive the field “paid_seat”. This field is not included in any other get-user calls inside the API, not specific user, or user by product. This is a problem. In February we had around 500 hundred users. W...
Guest over 7 years ago in Application 1 Unlikely to implement

Master Feature release should be automatically established from Feature release info (i.e. inherit the last of the due dates of the features)

It is extremely inconvenient and the cause of much manual reconciliation that the Master Feature release (and date) isn't *automatically* established as the latest of the related Feature releases (and dates). So can the Master Feature release rele...
Mark D over 7 years ago in Features 1 Unlikely to implement

Add optional date fields or ranges on Requirements

Allow Requirements under features to have Date fields. These could be locked to the feature's date range or allowed to fall outside depending on the organization and how they manage. This would allow for more granular reporting on Features, or t...
Travis Allen over 7 years ago in Features 4 Unlikely to implement

Quick way to reference existing Personas within Features and Requirements.

As a product manager, every day I am creating a new initiative (less often), feature and requirement. In the writing of User Stories, whether it's a feature or a requirement in Aha!, best practice is to mention the person for which the feature wil...
Matt Wagnon over 7 years ago in Features 3 Unlikely to implement

Update status of requirements on status change of feature

I don't want to change the status of each and every requirement individually when changing the status of a feature. For example, when I hand off a feature - which has 5 requirements, for example - to engineering to spike, they come back with a ful...
Guest about 9 years ago in Features 4 Unlikely to implement

Increase the maximum number of slides/pages in a notebook beyond 40

We have a large organization with multiple divisions under using Aha!. Need to create a single Notebook that can host all Roadmaps for specific division for easy access. Limit of 40 is very low. Need this to be in 80-100 range.
Rishi Patel over 7 years ago in Presentations 0 Unlikely to implement

Display release theme on feature board

The feature board shows a column for each release, but unless you name the releases to be identifiable (I use release versions), then it's hard to quickly see the theme of each release. It would be good to have the option of displaying the release...
Kristian Kauper over 9 years ago in Features 0 Unlikely to implement

View all To-Do's related to a feature and its requirements in one place

We've both added To-Do's to a feature's requirements and to the feature itself. I want to see a summary of all the To-Do's in a feature AND in a feature's requirements. Feature-level To-Do's are broader and about resolving the business need, prior...
Suzanne Vaughan over 9 years ago in To-dos 1 Unlikely to implement

Advanced product permissions for users

I like that Aha! allows me to share my product data with my organization, but I need more granular controls over who can create, read, update, and delete data. It would be great if I could create custom roles and assign them to users. Additionally...
Nathaniel Collum over 5 years ago in Account settings 1 Unlikely to implement

Add feature type icons to Features > Board

On the feature board, in the small card size view, adding feature type icons would make it a much better view for getting an idea of what's going on in a release. Would be a nice alternative to text description of feature for the large card size v...
Suzanne Vaughan over 9 years ago in Backlogs 0 Unlikely to implement