ADD A NEW IDEA

Application

Showing 7147 of 8637

Allow Aha! Fields in Strategy Templates

We are building out Models & Positioning Templates for our Teams to use that will reference the different Competitor & Persona Profiles but with no way to actually link the records. Templates only allow you to add blank component section...
Guest about 5 years ago in Strategy 0 Future consideration

Group the workflow board by status category

Our development workflow has many granular states, like "Ready for testing", "Testing in progress", and "Testing failed." With this granularity, we don't have to ask developers about where the feature is – the status gives us enough information. H...
Jeff Tucker over 2 years ago in Workflow boards 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 almost 7 years ago in Application 1 Future consideration

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

Need proper notifications for Workspace users when new Idea is posted in the portal

We have an internal feedback portal where people from various teams (Sales, CS, Support, AMs) post their ideas and feedback for our product. Our product team can't keep frequently checking the workspace for new Ideas added. So the product team nee...
Guest over 1 year ago in Ideas portal 0 Already exists

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 almost 7 years ago in Features 3 Unlikely to implement

Ability to create a new release without a release date defined

When you create a new release, you have to populate a release date. Often we create releases ahead of release planning and when dates aren't agreed. By having to populate a release date, this causes confusion as some people think the date is agree...
Julie Edwards over 1 year ago in Releases 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 almost 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 almost 7 years ago in Roadmaps 5 Future consideration

allow a scorecard to count the number of tags in a field and incorporate that into the score

This is a spin-off to the ideas that request that "custom fields" be incorporate-able into a score. It would be great if it wasn't just hard-entered integers, but anything that could be counted. For example, we use a tag field to indicate which o...
Oleg Yazvin about 5 years ago in Epic 2 Future consideration