ADD A NEW IDEA

Application

Showing 7523

Prevent Reviewers from changing the visibility of their own ideas

All my internal users are Reviewers, as I want them to be able to see more in depth information than they can get through the idea portal. However, I don't want anyone but an Owner to be able to mark and idea as Visible to Anyone. Internal employe...
Bryan Young over 5 years ago in Ideas 0 Future consideration

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

Move attachments (mockups) from feature to requirement

In the process of defining features, I create mockups and attach other files supporting the feature. Later, I'll break down the feature into product backlog items and I use requirements for that. It would be so awesome if there was a way to move a...
Tom Beck over 6 years ago in Features 2 Future consideration

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

Have an option to remove the redline (that represents the current day) on reports

When exporting, often the reports are viewed days or weeks after the initial export. The red line causes confusion and also is a poor visual experience for viewers of our reports and roadmaps.
Guest over 7 years ago in Roadmaps 5 Future consideration

Ability to view and edit "people" without having to go to a capacity report

Currently the only way to edit "people" is to go to their team in the config, or via a capacity report. eg change their schedule. It would seem to make more sense to see this data in the users profile (with the correct permissions).
Jason Hollis almost 2 years ago in Capacity planning / Development 0 Future consideration

Keep notification's email subject consistent to allow email threads/conversations instead of single emails per change

As a user, I would have all the notifications email for specific ideas or releases in a single conversation/thread. In Gmail, if I receive multiple emails with the same subject, they get grouped in a conversation/thread. To do this, I believe the ...
Adrian Romero over 4 years ago in Comments / Notifications 0 Future consideration

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