Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9173

Allow Consent to be mandatory

In the ideas portal admin area (settings/users/privacy) is the "Consent" item. Currently consent can be requested. Is it possible to make it mandatory? So that the following is forced when submitting the Idea? (see attachment). <p>By checkin...
Peter Farwell about 4 years ago in Ideas portal 1 Future consideration

Allow editing of custom fields within layout builder

Currently some layouts allow you to edit custom fields within the builder. It would be very useful to have the ability to edit all custom fields while creating custom layouts.
Jessica Murray about 4 years ago in Account settings 0 Future consideration

Calculate Epic Completion Based on JIRA Epic Completion

The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...
Rachelle S about 2 years ago in Jira 0 Already exists

Filters - "Is Not" Option

Hi Aha! Team, Having a filter that ommits certain options would help with reporting.
Jonathan Beggs about 2 years ago in Reports 0 Already exists

Add a full cycle product management in the process, including product design.

The cycle is great, but one key element is missing - it's the Product Design phase. I have to put it in "features" or "requirements", but design doesn't work like that. I'm unable to see/ demonstrate the work done by the design team, as there is n...
Guest about 2 years ago in Application 3 Already exists

Delivery risks: allow me to choose any date field (standard or custom) to use for the delivery risk check

Delivery risks are calculated against the due date of epics and features. Requirements don't have due dates, so this risk check is not present. I see two use cases here: If I have custom date field on a requirement, it would be great to be able to...
Dale Potter about 2 years ago in  0 Future consideration

Comments should not be editable by anyone except the creator of the comment.

It does not seem right that anyone with access to our Aha environment should be able to edit someone else's comment. While notifications and history on the object may help identify when such a thing happens. But not having that ability to begin wi...
Guest about 6 years ago in Comments / Notifications 0 Already exists

Manage external users to view presentations

We are looking to share a roadmap with external stakeholders from Aha. However, we want to control which external users can access in the case if an employee leaves on of our clients, we do not want them to retain access of our roadmap. Today, the...
Blake Falanga about 2 years ago in Presentations 1 Already exists

Add user first name and last name fields to Get User API response

Currently Aha stores user first and last names. In the get user and list users REST API response objects, those fields are combined into one field: name. So John and Doe just get returned as John Doe. This causes problems when you have many differ...
Guest about 2 years ago in API 0 Future consideration

Allow more than one column of features under one epic

Users can easily create new columns in their user story map. If a user adds two columns but only has one epic parent then assume all features under and to the right are children of that epic. It could be pseudo coded such as something like (featur...
Guest about 4 years ago in User story map 0 Future consideration
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2025 Aha! Labs Inc.•All rights reserved