All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5653
1
VOTE
2
VOTE
Develop an OSLC REST based connector for Aha!
We need to link Aha! Roadmap items to other items in Sparx EA (OSLC compliant) using ArchiMate 3.1 and an OSLC connector for Aha! will enable us to do that. This connector will also enable us to link Sparx EA ArchiMate 3.1 model elements such as s...
0
Future consideration
2
VOTE
New section under Strategy or Info for definitions/product functions.
Our Product has multiple functions/modules. With each module there are some terminologies and concepts that need to be defined. I can use notes to create a document but that that can get messy really quick. I see this area working similar to how P...
0
Future consideration
1
VOTE
Enable Google Keep Move and Pin
It would be great to allow for cards (epics, features, requirements) to move in any "card" based view. A great example is Google Keep (Web version on Desktop). Google Keep allows for easy moving of cards and pinning of favorites to the top. Add in...
0
Future consideration
1
VOTE
better validation warnings and units tips and handling on estimates fields
the toolips on estimates fields need consistent messaging in all field contexts, with proper messaging/tip content based on the units of the configuration. this needs to be the UX when creating (actual configured units not a hard-coded either/or t...
0
Future consideration
1
VOTE
please let admin better control the field choices on apply rank to users cannot make bad choice
apply rank opens a picker to let user decide which custom field to apply the rank value to , and that custom field needs to be the field in the mappings that provide update into target tooling (my case, its ADO, stack rank). I see multiple custom ...
0
Future consideration
1
VOTE
Allow using automation to change the parking lot of new features in Aha Develop
When creating automation for features in Aha Develop, it's not possible to change the parking lot (workspace) of the feature. There is a variety of fields that can be changed, but unfortunately, the parking lots are not among them. This would help...
0
Future consideration
2
VOTE
Block default customization from being modified
Anyone with customization permissions can modify the Default workflows, scorecards, time frames, etc. Without removing the option to set new default, why not blocking the default from being modified? this will allow an encourage users with the rig...
0
Future consideration
2
VOTE
Don't automatically open links in notes/descriptions in a new tab
When you try to open a link from a note/description in a new tab, some javascript automatically opens the link in a new tab and changes the focus to it. Opening a link in a new tab should be done in the background, like when done with the middle m...
0
Future consideration
2
VOTE
Allow each team to provide an independent set of tags on a feature
Looking at the tags field on a develop feature, it inherits all of the tags from my main roadmaps workspace. This isn't the behaviour I'd expect, I would expect a develop team to have its own unique set of tags of primary relevance to them. In pla...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved