Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 8599 of 8599

Add a standard Epic List under Feature menu

The current Feature menu doesn't provide an Epic List, and there is no way to see a list of Epics unless you create a custom list. It would be nice if you provide that as an option to include in the navigation to minimize having to create all thes...
Mousa Mitwasi over 3 years ago in Epic 1 Future consideration

Enable additional customization in Drawer Custom layout

Additional flexibility to move fields in between tabs or to the header where the description field is located. Currently, adding a lot of fields top-down becomes somewhat cumbersome to scroll through.
Mark Slykhouse over 3 years ago in Features 0 Future consideration

Markdown Fenced Code Blocks

It would be extremely helpful to support markdown fenced code blocks in a way that would allow them to correctly transition to GitHub via the GitHub integration. Currently GitHub supports these in their descriptions and if Aha imports these via th...
Guest over 3 years ago in Features 0 Future consideration

Lower Shipped Epics in Drop Down Lists

After you've been using Aha! for a while, the number of epics builds up. This can be come a hinderence when you are looking to add a feature to an epic and the drop down list has dozens of results. After speaking with Aha! engineers, it was pointe...
Guest over 3 years ago in Features 1 Future consideration

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

REST API indicates if custom field is read-only

Currently, the REST API doesn't indiciate if the given custom field has been defined as read-only or not. Here's a sample field definition for a read-only field as returned from `/api/v1/products/{productId}` {"id": "7002184427275897244","key": "k...
Tomasz Zarna over 2 years ago in API 0 Future consideration

Allow an Admin Response for Ideas that are "Unlikely to be..." or "Will not be Implemented" without exposing the idea to the Ideas Portal

Sometimes we will receive an idea that is either inappropriate for our product or we just have no plan to implement in the future. It would be great if we could give an Admin Response in this case as currently the submitter does not receive notifi...
Paul Ruddick about 5 years ago in Ideas 1 Future consideration

'Add Feature' button on List view

It would be helpful to have the option of an 'Add Feature' button within a list view. If only one epic is selected for the view, the Add Feature should automatically associate the new feature with that epic. If more than one epic is selected for t...
Guest 10 months ago in Features 0 Future consideration

Definitions in the application

Super helpful if could simply hover over something like 'Activities Board' and a quick defitition came up. Or at least there was an easier accessable glossary. It's not the most intuitive to find.
Guest over 2 years ago in Features 0 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