All ideas
Sort by:
Trending
Status:
Showing 9172
2
VOTE
1
VOTE
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...
0
Already exists
1
VOTE
1
VOTE
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...
3
Already exists
1
VOTE
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...
0
Future consideration
3
VOTE
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...
0
Already exists
1
VOTE
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...
1
Already exists
1
VOTE
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...
0
Future consideration
2
VOTE
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...
0
Future consideration
2
VOTE
Adding Validity date range to user access / authorizations
We should be able to add validity date range while giving access/authorizations to users. Many users require Aha! access for a limited period of time. This is will help us to keep the user list clean over a period of time. This also helps us to ke...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved