All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5653
2
VOTE
Firefox spell-check should work in the text editor
Many people, including those with disabilities, rely on spell checking feature provided by browsers to highlight spelling mistakes during text entry in we forms. However, Aha! text entry fields appear to reset the browser spell checking so highlig...
4
Future consideration
1
VOTE
Ability to search for workspaces in account settings
We often need to make changes to our workspaces/hierarchy. When doing so, it would be very helpful to be able to search workspaces from settings>account>customisations>workspaces. (https://companyname.aha.io/settings/account/projects)
0
Future consideration
1
VOTE
Feature History Changed to show Story History too - Needs a filter to filter to only feature
The Feature History has changed to also show Story/requirement History. This makes it hard to find the history of the feature or single level you are looking at. History needs a filter to filter to only 1 level and not the children levels.
0
Future consideration
1
VOTE
2
VOTE
Log Effort - Allow the configuration of quick actions to log typical time spent
It is possible to configure quick status transitions which is a very nice and quick way to change the status of an item in Aha. It would be excellent to have the ability to quickly log a preset amount of effort against a task as well. This button ...
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
1
VOTE
Better presentation of text when integrating to an existing field in ADO
Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved