All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5639
1
VOTE
Pivot Table Sort order flexibility
When selecting the sort order in a pivot table. It would be nice to select the order by the item. We find that in some cases sorting the order by least to greatest or A-Z does not adequately meet our needs. For example when a list is A,B,C,D,E we ...
0
Future consideration
4
VOTE
Assignee of feature in Aha! should propagate to Gitlab
As a user of Aha! / Gitlab integration, I would like to assign a feature in Aha to a specific user and have it show up as assigned to them in Gitlab, so that they are aware of the new feature and can take responsibility to break it down further in...
0
Future consideration
2
VOTE
Advanced Integration with Zapier
I was trying to do an integration between Freshdesk and Aha, and since there is no direct integration, I used Zapier, however, the fields available at Zapier are just the idea title and description, all the custom fields I have on Aha's ideas are ...
0
Future consideration
2
VOTE
Capacity planning by half (instead of by month)
At the initiative level, we plan 6-12 months into the upcoming fiscal year, by half. We estimate team capacity (high-level t-shirt sizing) by 1H and 2H. Our goal is to know the right scope moving forward and balance our engineering capacity for 1H...
0
Future consideration
2
VOTE
Mass Update of Workspace custom fields
As a user, I need the ability to do a mass update on Workspace custom fields so that we can utilize those fields for reporting. All of our products have specific business programs and business segments so we created a custom field to capture progr...
0
Future consideration
3
VOTE
improved metadata rest services for fields
For users trying to interface with the Aha service via the rest services there is a definite lack of available services for fields.
There needs to be a way to validate fields being sent to Aha. Currently there are only services that return filed d...
1
Future consideration
2
VOTE
2
VOTE
Allow Jira-related fields to be included in automation rules
It would be helpful for fields like the Jira key or integration link to be available in automation rules. That would enable my team to create triggers that look at when an integration link is changed or is no longer available.
0
Future consideration
2
VOTE
Allow for null Release Date
Currently the release date field is required. But usually when a release is first written up there is no realistic idea for when it might be delivered. For releases that are postponed or of lower priority, the initial entered dates which seemed so...
0
Future consideration
1
VOTE
Provide "Confidential" as a watermark on printed/pdf roadmaps
We wanted to send a pdf copy of the strategic roadmap to a partner however it would be nice to put a watermark on it so we can identify it's confidential. As a stretch if we could even customize it then we could put the partner's name on it.
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved