All ideas
Sort by:
Trending
Status:
Planning to implement
Showing 29
4
VOTE
Light grey text is illegible to visually impaired users
Currently, in an integration, when the settings are locked (e.g. the project to which it is integrated) the text is shown in a light grey to indicate the settings cannot be changed. This creates a challenge for users who are color blind or otherwi...
0
Planning to implement
7
VOTE
Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
0
Planning to implement
21
VOTE
1
VOTE
Allow reporting on todos on Key Results
What is the challenge? I am unable to create a report on todos on Key Results. When I attempt to create a report with Todos as the primary record, Key Results are not an option for the secondary record. What is the impact? I am unable to track tod...
0
Planning to implement
17
VOTE
Support approval gates in Aha! Develop
Quality is critical for my product. I want to ensure that all features go through QA testing before being marked as "done". The approval workflows implemented by Aha! Roadmaps solve my need well. I want Aha! Develop to respect those workflows as w...
1
Planning to implement
4
VOTE
Improve performance of workspace picker
What is the challenge? We have a lot of workspaces in our account. Sometimes it can take up over a minute for the workspace picker to open. What is the impact? The long loading times hurt productivity. Describe your idea Please make the workspace ...
0
Planning to implement
9
VOTE
Allow start and due dates to be set to a specific date in automation rule actions
It appears that right now, the actions available in automation rules when updating a date field (Start and due dates in particular) are all relative to the current date (e.g. set to 1 month from the current date, set to 1 week from the current dat...
6
Planning to implement
1
VOTE
Users API does not consider "Knowledge" License as Paid Seat
What is the challenge? paid_seat field is not properly returned for the new "Knowledge" license What is the impact? We cannot rely on API data alone and need to find workarounds in this case to properly reflect the users license information Descri...
0
Planning to implement
2
VOTE
9
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
© 2025 Aha! Labs Inc.•All rights reserved