All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5643
4
VOTE
Allow all approvers to respond to a to-do regardless if someone already "rejects"
What is the challenge? When a to-do is assigned to multiple approvers, if the first approver rejects the to-do, the remaining approvers are unable to respond to the to-do. What is the impact? The remaining approvers do not have the option to provi...
0
Future consideration
80
VOTE
Password protection for "Share as webpage"
Previously, we heavily used the "notebooks" feature to publish a scrollable webpage view of our feature lists for our Engineering teams that we didn't want to give access to our main Aha account. Now that "notebooks" have morphed into "presentatio...
21
Future consideration
1
VOTE
Do not highlight "Potential duplicates" across workspaces
What is the challenge? There is a feature which displays in a request with text of "Potential duplicates were discovered." By clicking on a hypertext link of 'Review', there is a display of the potential duplicates. This feature is useful only whe...
0
Future consideration
7
VOTE
Add support for key results in Automations
What is the challenge? Now that we have the ability to cascade Goals/Initiatives from an Epic to its related Features, we need the ability to cascade Key Results as well to complete the Strategic Alignment picture What is the impact? Only cascadin...
4
Future consideration
6
VOTE
Ensure features and epics roll up to an objective/initiative pair
What is the challenge? We've defined a set of objectives (goals) and a set of initiatives under each goal. But the UI allows epic and feature creators to select objectives and initiatives that are independent of one another. What is the impact? Th...
0
Future consideration
12
VOTE
Allow KB users to give feedback on notes
What is the challenge? Those managing a KB want to know if pages are helpful to their end users, but there currently is not way to ask for feedback. How would you solve it? Add a widget at the bottom of each KB page to ask for feedback. This could...
1
Future consideration
79
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
3
VOTE
Add tooltip to the dependency line checkbox for custom roadmaps
What is the challenge? Currently dependency lines only show for the primary record in a report, not necessarily for the record shown in the bars What is the impact? This is confusing as it's not explained clearly Describe your idea Add a tooltip o...
0
Future consideration
12
VOTE
Microsoft Teams Copilot Integration
Who would benefit? Product Managers What impact would it make? PdMs would benefit to have line-of-sight for updates that could impact them and their system of responsibility (“Copilot, tell me when the networking team will be upgrading their exter...
0
Future consideration
1
VOTE
Bring custom fields into release templates
What is the challenge? https://big.ideas.aha.io/ideas/APP-I-2291 saw the addition of custom fields to to-dos which is great. We have added one for 'department responsible' so we can use this in reporting however it is not possible to set this up w...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved