Application
Sort by:
Trending
Status:
Unlikely to implement
Showing 7702
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
28
VOTE
32
VOTE
Link a Feature to multiple products
We regularly release features across Desktop, Web and Mobile which we have as separate products in aha. We would prefer to be able to have a feature which is linked across all products, as all are updated at the same time. We currently add feature...
11
Unlikely to implement
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
3
VOTE
8
VOTE
Custom Field - Internal Name & Choice Lists Report Display
When creating reports with custom fields, there can be many fields within an account that have similar names that will display as field options. We use the internal name to help differentiate and allow the user to select the right field they are l...
0
Planning to implement
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
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
22
VOTE
© 2025 Aha! Labs Inc.•All rights reserved