All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5639
3
VOTE
Converting sticky notes to other record types should not bypass any required fields processes
When converting sticky notes in a whiteboard to other record types, we don't want users to be able to bypass required field entry for those record types. I have found other areas within Aha! where required field entry can be bypassed when creating...
0
Future consideration
3
VOTE
Add better error handling for 'unhandled error exceptions'
When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
0
Future consideration
4
VOTE
Ability to filter on reference num
It would be incredibly helpful to be able to filter a report based on a list of specific reference num values (we especially need this at the feature level, but I imagine this would be useful for all objects). Ideally this would be a list of exist...
1
Future consideration
10
VOTE
Trending Graph for the Dashboard of point in time stats
I like the Dashboard feature, but I'm forced to pull my numbers into Excel because there is no way in AHA to tell it to grab the last day of the month for each of my record counts and produce a line graph. It would be really great to be able to sh...
1
Future consideration
4
VOTE
Display Dashboards / Webpages in Tableau
For security reasons, we cannot have Aha! set to "allow anyone to access." Still, we need the ability to provide a seamless experience for our Executives and users to derive value from the Aha! data. We want to be able to display these in Tableau ...
2
Future consideration
15
VOTE
Allow for mapping to-dos in Asana integration
In some cases, Asana sub-tasks are more closely related to Aha! to-dos than requirements. For example, a feature may have to-dos related to marketing tasks which need to sync with Asana.
An option to map To-dos to Tasks or Subtask would provide a ...
4
Future consideration
2
VOTE
Ability to report on workspace line custom fields in a record hierarchy
Who would benefit? Product Managers, Programme Managers, Project Managers What impact would it make? You could add custom fields at a workspace line level and be able to report on this information at higher-levels of your record hierarchy How shou...
0
Future consideration
9
VOTE
9
VOTE
Display Acceptance Criteria below description
When we review features with stakeholders, we need to consider and refine both the description (user problem) and the acceptance criteria (definition of done) before it can be approved. We also need the acceptance criteria to sync to an equivalent...
1
Future consideration
8
VOTE
Support linking the Aha! URL field to the Azure DevOps Hyperlink field
Goal: We want to see in DevOps which Item it syncs with in Aha! Current set up: Aha! URL field linked to Hyperlink field in DevOps Challenge: We are using the hyperlink field to capture URLs to multiple sources. This is all being done in a single ...
2
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved