ADD A NEW IDEA

Application

Showing 770

Convert Requirement into an Idea (instead of a Feature)

There is already a similar thing to downgrade a feature to an idea. The justification is this - We create an idea for a feature Once we understand it enough to decide if we are going ahead with it, we will commit resource to properly planning ...
Guest almost 8 years ago in Releases 0 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 almost 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 about 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 about 7 years ago in Features 3 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 about 7 years ago in Presentations 0 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 almost 9 years ago in Features 4 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

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 about 9 years ago in Features 0 Unlikely to implement

Add voting limitation by company/email domain

As a user, I would like to have the ability to define number of votes available by the company or email domain of my portal users, so that I can provide a balance between larger and smaller customers. Our client sizes can vary significantly, so wh...
Norah Brennan over 6 years ago in Voting 0 Unlikely to implement

Would like a setting to control the default ranking of new Features

Currently, new Features that are created or promoted from Ideas into a Release or Parking Lot are put at the top of the list and given the highest ranking. Would like to have a setting to control this, as we would prefer that new Features that are...
cheryl fetchko over 6 years ago in Features 1 Unlikely to implement