All ideas
Sort by:
Trending
Status:
Showing 9110
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
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
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
Access your custom layouts to configure the Related tab for a record - be able to do this for linked records
Who would benefit? Product Owners/Managers What impact would it make? Easily be able to access linked record information from within the parent record such as engineering phase and engineering target date (custom fields.) How should it work? Enabl...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved