Pinned ideas
PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
All ideas
Sort by:
Trending
Status:
Showing 9641
1
VOTE
View Only Permission between Roadmaps and Develop
What is the challenge?
Currently, it’s not possible to allow users to assign work to a team while preventing them from updating the team’s status.
What is the impact?
This inadvertently allows someone from another workspace to modify the s...
0
Future consideration
2
VOTE
Dynamically create key results from key results field
What is the challenge?
As new tactical records are being input there are times where new key results are being defined. Today a user would need to go to the objective, then create the key result, then go back to the tactical record and associate...
0
Future consideration
2
VOTE
Ability to collect feedback from users via a form/poll within your Aha! account
What is the challenge?
A way to consistently gather usability feedback from users
What is the impact?
Users share usability challenges in email, IMs or sometimes in meetings (Data is inconsistent)
Describe your idea
A feature that ca...
0
Future consideration
2
VOTE
Collapsible sections/headings in Notes to improve content creation & reading
What is the challenge?
Long notes become unwieldy to write, read, and edit. This makes it difficult to review, consume and share detailed content.
What is the impact?
The lack of collapsible sections and document navigation menu means one ...
0
Future consideration
3
VOTE
Display Team fields on Requirements associated with Develop/Teamwork Parking Lot Features
What is the challenge?
Currently, the Team fields do not display on Requirement records if the parent Feature is a Develop/Teamwork Parking Lot feature; however it does display on the Feature's Requirements if the record is assigned to the Team ...
0
Future consideration
83
VOTE
User Story Mapping for Features/Requirements
Admins should have the ability to chose which records are in the User Story Mapping. We structure Aha! so that User Stories are at the Requirement Level so it makes sense for us to view as Features/Requirements
We don't use Master Features &...
14
Future consideration
4
VOTE
Include history of comments when importing from ADO integration
What is the challenge?
Currently, when importing ADO records via an ADO integration only the latest comment is imported from ADO
What is the impact?
Inability to see comment history can lose critical context and require Aha! users to go to...
0
Future consideration
7
VOTE
Delete in Aha restricted to Admins expand to Custom roles
What is the challenge? Recently Aha! implemented a feature for restricting delete but once enabled only Admins can delete records. What is the impact? We have some power users who required delete permissions but do not need other admin priviliges ...
0
Future consideration
94
VOTE
Update idea status when promoting to an existing feature
When I promote an idea to a new feature, the status of the idea changes to the first one in the workflow that equates to “in progress”. When I promote an idea the an existing feature, however, the status does not change. I think promoting to an ex...
15
Likely to implement
13
VOTE
Use the release "Date range" in automations
What is the challenge? Trying to configure a release automation to set the "Feature start date" and "Feature due date" to be the same as the "Release start date" and "Release due date" What is the impact? Using custom/alternate fields where this i...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved