All ideas
Sort by:
Popular
Status:
Future consideration
Showing 6217
4
VOTE
Add planning poker to Aha! Whiteboards
What is the challenge? In PI planning sessions, I often need to get the feedback of multiple users to know the number of story points to assign to a piece of work. This cannot be a collaborative process in Aha! today so teams may resort to outside...
0
Future consideration
4
VOTE
Allow custom colors for custom table many-to-many fields
What is the challenge? I've set up a many-to-many custom table field to take the place of a multi-select custom field. I can't change the color of the custom table entries, like I could with the multi-select tags. It makes it difficult to quickly ...
0
Future consideration
4
VOTE
Bulk import from HTML or JSON into notes
What is the challenge? Moving from a different KB source into Aha! Knowledge requires manual copying, pasting, and reformatting. How would you solve it? An import tool that accepts HTML or JSON would speed up this process. What impact would it mak...
0
Future consideration
4
VOTE
Add option to delete child notes when deleting a folder
In Knowledge, when a folder is deleted, the child folders/notes are not deleted with it. It would be helpful to present the user with an option in a modal to delete just the folder, or delete the child folders/notes as well. Though you can use Shi...
0
Future consideration
4
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
4
VOTE
Reference key results in worksheet equations
Who would benefit? Everyone tracking OKRs in Aha! Roadmaps What impact would it make? Allow teams to leverage the power of worksheets to perform custom calculations on their key result data How should it work? Support referencing key results in wo...
0
Future consideration
4
VOTE
Allow automations for custom tables based on another custom table
Who would benefit? Aha! users who have expanded their capabilities through multiple custom tables. Today, when custom tables reference each other, you need to update them on both sides. This drives no-value-add manual work and is ripe for inaccura...
1
Future consideration
4
VOTE
Remove releases from features roadmap if all features/epics have been filtered out
Who would benefit? Product managers & their shared webpages What impact would it make? Allow us to not have to manually adjust releases based on goals/initiatives or other information that's not represented in that release How should it work? ...
0
Future consideration
4
VOTE
If you link an initiative to an epic, it would be nice the features linked to the epic are automatically linked to the initiative
Who would benefit? Product owners What impact would it make? Less manual work How should it work? Link epic to an initiative Pop up to link the features as well (cfr when you move an epic to another release) Without use of automation rule (no ente...
0
Future consideration
4
VOTE
Provide additional formatting controls to the Now, Next, Later Roadmap view, similar to Pivot Chart functionality
Who would benefit? Any user who is using the Now, Next, Later roadmap, or those who are creating their own version with a Pivot table. What impact would it make? It would allow users to more fully customize Now, Next, Later roadmap view to tailor ...
0
Future consideration