All ideas
Sort by:
Trending
Status:
Showing 9173
35
VOTE
Restrict the visibility of specific custom fields to different users
We use Aha! for all our product planning, however we currently do some financial estimates outside of Aha! which we don't want to share with the wider development team. This causes us to fragment our data and use permissions in other portals as th...
8
Future consideration
11
VOTE
Include Belongs To in record link reporting
Who would benefit? All teams who create parent-child relationships What impact would it make? It would help teams who are using record link reporting to validate data relationships How should it work? In the attached example, a feature belongs to ...
2
Future consideration
8
VOTE
Intelligently reduce fields shown when adding fields to a report
What is the challenge? When I am building a report, every time I go to add a field to a report, I get a dropdown showing every possible field associated with that record. Fields for every custom workflow for every workflow in the account, tons of ...
2
Future consideration
6
VOTE
Remove extra whitespace in resized embedded views when exporting to PDF
What is the challenge? If you have a note with an embedded view configured to resize to fit when publishing, there is usually extra whitespace at the bottom of any view that had to resize (wider and taller than the page). What is the impact? It lo...
0
Future consideration
7
VOTE
Add a TO-DOS icon on the card layout
What is the challenge? User has to go into the card details to check if there are any TO-DOS. What is the impact? Adding an icon on the card layout that will display the number of TO-DOS for that feature will have a time saving impact. Describe yo...
0
Future consideration
7
VOTE
Install new fonts for Knowledge Base
What is the challenge? We would like to use a Knowledge Base for external user access; however, without the ability to use our branded font, it is a challenge What is the impact? Misalignment with branding materials Describe your idea We would lik...
0
Future consideration
7
VOTE
Calculate Release Date Range from Epics
What is the challenge? There are teams who only use Epics in their workspaces, but the date range of Releases can only be calculated from Features. Moreover, there are no automation rules or integration mapping options to automatically update the ...
3
Future consideration
41
VOTE
Capacity for teams: Estimate in skills
Capacity for teams currently allows you to create teams and add detailed estimates to records. However, we have a challenge with the way a team's capacity is calculated. We have cross-functional teams, which include people in product management, Q...
2
Future consideration
4
VOTE
Persist the relationship between feature and related idea created from it
Using the 'Create related idea' option within a feature creates an idea that is promoted to that feature, and shows it in the Research tab of the feature. But if the idea is then promoted to a different feature afterwards, there will be no visible...
1
Future consideration
4
VOTE
Sync comments between Jira & Aha!
What is the challenge? Unable to Sync deleted and edited comments between Jira and Aha! What is the impact? Syncing deleted and edited comments between Jira and Aha! is crucial to maintaining accurate and up-to-date communication across teams. If ...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved