All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5643
14
VOTE
Add support to map Azure Boolean Fields to Aha
This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...
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
15
VOTE
Custom field tied to a custom table should show all columns (or selected columns) from the table
We have a custom table with 4 different columns and a custom field (feature level) tied to this custom table to select a value. When I access custom field for selection, it only shows the first column in the table. However, I need to see all colum...
0
Future consideration
19
VOTE
Automation to set a default estimate for all features created
I'd like the ability to set a default estimate for all features created. I checked the automation rules and the estimate field is not an option to update via automation rules. Some of our teams are doing a no estimates style of capacity planning w...
2
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
23
VOTE
Allow multiple persona types to coexist for Products, Product Lines, etc
We need to be able to define multiple personas for individual products or product lines - currently only one template can be used for these entities. In addition to the user personas already in the system, we also need to have Buyer and Enterprise...
2
Future consideration
17
VOTE
View in Aha! the author of a comment created in Azure DevOps
In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
1
Future consideration
11
VOTE
Ability to add an epic to a release phase
We use Aha Roadmaps for our roadmap and release planning, with detailed phases that cover development actitivies as well as Go to Market release planning. Currently we run into the problem that since half of our teams use Jira to track their work,...
0
Future consideration
3
VOTE
Create Custom Layouts for Custom Tables
What is the challenge? I can´t create custom layouts for custom tables What is the impact? I can´t group fields depending on the end user priorities, I can´t turn field to read-only if needed, I can´t edit relationship data with other records Desc...
0
Future consideration
3
VOTE
Support changing embedded report type
What is the challenge? If you create a custom report and add it as an Aha! view to a note, if you untick 'Create a copy', and then change the report to a different type (such as changing from pivot to list) it stops displaying properly in the note...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved