Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Application

Showing 7746

New User Story Map entered Epics should still require required fields and load the standard description field template

Problem: When adding entities (e.g., Epics) via the User Story Map, the user is not prompted to enter in required fields and the predefined Epic template is not loaded in the description field. This bypasses the Epic creation protocols elsewhere i...
Peter Bongiorno about 3 years ago in User story map 0 Future consideration

Adding Feature Workflows for Feature Types

Aha! allows you to create feature workflows for a product, but not for a feature type. It would be helpful to have product workflows applicable beyond the product - allowing users to customize completion workflows per feature type. Let's look at ...
Max Chanoch almost 10 years ago in Features 4 Future consideration

Group Custom Fields into sections

Very similar to APP-I-2199 I want to be able to group custom fields into distinct groups. For example I have a section that is all dates controlled by our development team. I would like to take those fields and group them together into one section...
Guest about 9 years ago in Features 1 Already exists

Example Dashboards

Loving Aha! dashboards! They are a great way to communicate progress and status to stakeholders. When adding a new dashboard, there are suggested example panels that can be included. This is great, but I would love to see complete example dashboar...
Shawn Zenz over 4 years ago in Reports 0 Future consideration

Rename empathy sessions

Who would benefit? Align terminology with what we use it for Early adopter/BETA What impact would it make? Make it easier for the team to adopt it How should it work? Custom terminology like other aha! features.
Guest 12 months ago in Empathy sessions 0 Future consideration

Add Support for Workspace Rules in Automations

Who would benefit? All users What impact would it make? We currently have custom fields at the workspace level and would like to be able to create automations based on when those fields are changed. For example: We have a custom user field "Progra...
David Willequer over 1 year ago in Application 1 Future consideration

Prioritization Report - Allow more than one level of record structure

On the feature prioritization report, under the “edit columns” option, when I select “+ Add records related to this epic” it returns a blank list. I’d like to add initiatives to this list. This is needed when Epics are linked to Initiatives, but n...
Evan Hollohan 12 months ago in Features 0 Future consideration

Provide a setting to add new Epics and Features to the Epic/Feature roadmap without user action

We have a very large Epics roadmap, new Epics are added to releases by the team very frequently. We want a setting that shows all new records added to releases in the roadmap shown in webpages and presentations. It is not reasonable for someone to...
Valentina Morales 12 months ago in Roadmaps 0 Future consideration

Allow a field to be re-used across multiple sections of a dynamic ideas form

We currently use dynamic forms within our ideas portal. We've structured our forms such that we gather initial information and then direct the user to one of 6 branches, where specific information is captured relative to that branch. We would like...
Mark Eaves almost 3 years ago in Ideas 0 Future consideration

Hide shipped master feature in feature form

When I link a feature to a master feature, I want to see only current master features (and not shipped master feature)
Guest over 5 years ago in Features 4 Future consideration