All ideas
Sort by:
Trending
Status:
Unlikely to implement
Showing 1498
2
VOTE
Remove "Product Line" from reports that have different names for a Product Line
We have used "Product Line" to define teams within Aha in order to organise our PM's work into a more intuitive hierarchy (for them). However, when we create a Pivot Report, "Team" includes "Product Line" in parenthesis. It would be great if that ...
0
Unlikely to implement
3
VOTE
2
VOTE
Security per Feature or per Release
To enable consultants and freelancers to also provide estimates and work using Aha!, please implement more fine-grained security features to add user and choose from a list of features they are allowed to see and contribute. This is critical to en...
3
Unlikely to implement
2
VOTE
Integrate with Scrumdo.com
This tool is a great way to have delivery and product planned into one. The Aha! tool is a tremendous product in the sense of organizing and structuring the features and initiative of a product management team with the Agile mindset. Scrumdo takes...
0
Unlikely to implement
2
VOTE
Restrict access to bulk actions
We have 20+ people in Contributor role working on the same Product. All of them have by design access to bulk actions and can inadvertably bulk delete all of the hundreds of items that we have in Aha!. We want to somehow restrict access to bulk ac...
0
Unlikely to implement
2
VOTE
Human friendly API Product IDs
This benefits developers who would like to increase the functionality of Aha! applications, which in turn benefits all the Aha users at large by making everyone more productive!
Currently, the Aha! API User endpoints that return product_ids gives ...
0
Unlikely to implement
2
VOTE
Maintain overlapping release dependencies
As a user planning a release, I want to have my release phases overlapping finish-to-finish with a lag time defined so the dependencies maintain the overlap that is initially set with the dependency so that I can more realistically represent the o...
0
Unlikely to implement
2
VOTE
Innovate capacity planning and release planning - plan features to multiple releases
CAPACITY PLANNING/TRACKING/REVIEW There is a very frustrating situation when capacity planning done in the beginning of the release can not be persisted by the end of the release when you have undelivered features and have to move them to another ...
1
Unlikely to implement
3
VOTE
2
VOTE
Behavior of bulk edit product permission "to none" is not consistent with "from none"
When bulk edit product permission to viewer or product owner for example, product line permission of "none user" will change to the new value accordingly while other users will keep their their individually assigned permissions. This is ...
0
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved