All ideas
Sort by:
Trending
Status:
Unlikely to implement
Showing 1526
3
VOTE
Visualisations: Circular Dependencies
Dependencies are created using the “link to another record” feature.
It is not possible to create circular dependencies with itself.
It is possible to create circular dependencies in Aha when it is as a result of another record.
When you visualise...
0
Unlikely to implement
4
VOTE
4
VOTE
Extend product tree to support different configurations of a product line
I manage a product line where each product has different configurations. Currently I get around it by making different releases, but it really doesn't solve the problem because the different configurations have different requirements. So, being ab...
1
Unlikely to implement
3
VOTE
Limit AHA commands in Slack
Im trying out the new Slack to AHA integration - it works great but is it possible to limit the interactions a user can make with AHA? I want to limit my teams options to just being able to raise ideas through slack - and not iniatives/releases et...
0
Unlikely to implement
4
VOTE
In workflows, add the ability to limit setting a certain status to certain users.
In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless.
If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets v...
2
Unlikely to implement
1
VOTE
User Management moved from Main Menu to Product line settings
I have to manage more than 100+ users on a regular basis in Aha!. With the latest change, the Users tab has been moved to Product Line/Product which is adding to number of clicks everytime to add/manage/remove users. To add to the pain, there is n...
1
Unlikely to implement
3
VOTE
Automate service account password updates for TFS integrations
Right now we have a TFS integration configured with Aha which requires us to use an AD service account for TFS. This service account password needs to be manually added within Aha! however we have a policy that all our service accounts require pas...
0
Unlikely to implement
4
VOTE
Features should Inherit initiatives from Release & Master Release so all Pivotal stories are under the Epic after sending to PT (and the Epic is actually created)
When pushing a feature to Pivotal Tracker, a user can select a mapping that allows for initiatives to be mapped to epics. The only initiatives this works for are initiatives directly referenced by a Feature. Any initiatives referenced by the Relea...
7
Unlikely to implement
4
VOTE
4
VOTE
© 2025 Aha! Labs Inc.•All rights reserved