All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5653
11
VOTE
Allow "Original Estimate and "Logged Effort" to be used in Calculated Columns
In Roadmaps list, having the ability to do calculated columns is incredibly powerful. However, we recently noticed that there are two fields we want to use to create charts that are not available to use. These are Original Estimate and Logged Effo...
1
Future consideration
3
VOTE
4
VOTE
Allow Drill-in for Feature columns on Prioritization view
Who would benefit? Users sharing Prioritization views via shared webpage What impact would it make? Increase ease of use for drill-in functionality by enabling the function on the default columns How should it work? The default Feature Name column...
0
Future consideration
31
VOTE
21
VOTE
Fix critical Aha to VSTS Integration not syncing Feature Order
We are trying sync the Feature order from Aha to VSTS (never the other way around).
Keeping the Features in VSTS in the same order in Aha is in our use case, critical to using the integration.
The reason that it fails is because matching the Aha R...
2
Future consideration
3
VOTE
Prioritization Report - Allow more than one level of record structure
On the feature prioritization report, under the “edit columns” option, when I select “+ Add records related to this epic” it returns a blank list. I’d like to add initiatives to this list. This is needed when Epics are linked to Initiatives, but n...
0
Future consideration
3
VOTE
Provide a setting to add new Epics and Features to the Epic/Feature roadmap without user action
We have a very large Epics roadmap, new Epics are added to releases by the team very frequently. We want a setting that shows all new records added to releases in the roadmap shown in webpages and presentations. It is not reasonable for someone to...
0
Future consideration
15
VOTE
Sync releases for Azure DevOps integration
Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...
0
Future consideration
2
VOTE
Many-to-one custom fields should be clickable (like many-to-many custom fields are
What is the challenge? When accessing records in a custom table, if many-to-many custom fields are used, you can single-click the field on a record or in a report to open the context card. This does not work for many-to-one custom fields. What is ...
0
Future consideration
6
VOTE
Allow detailed estimates to affect capacity plans without needing to assign a team member to the Aha record
We do all of our assigning in Jira, and in fact only sync epics between Aha and Jira, so adding an assignee in Aha doesn't make sense for us as you don't assign a dev to an epic, even in Jira. We assign to the task/sub-task. Having to add an assig...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved