All ideas
Sort by:
Trending
Filter by:
Status
Showing 9701 of 9701
8
VOTE
Whiteboard timelines should match fiscal year setting of Aha! account
Who would benefit? Customers whose fiscal year does not align to the calendar year What impact would it make? Currently, the timeline shape available for whiteboards shows a quarterly breakdown, but for teams with fiscal year start that is not Jan...
2
Future consideration
16
VOTE
Allow record mapping to Asana Projects
Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every ...
0
Future consideration
29
VOTE
Remove "Show/Hide Parking Lots" setting from Releases > Gantt view
The Releases Settings dropdown on Releases > Gantt includes two options:
Show/Hide Shipped releases
Show/Hide Parking lots
Showing/Hiding shipped releases makes sense since a shipped release is date-bound, so a Gantt view can display it. But...
7
Future consideration
26
VOTE
Ability to Customize Formatting on Layouts
It would be useful to be able to customize layouts. For example, add section markers to separate fields for a more organized view, add helper text underneath field names that doesn't disappear as soon as the user starts typing, and arrange related...
4
Future consideration
6
VOTE
Add support for displaying milestones in the Now, Next, Later roadmap
What is the challenge? Highlighting key upcoming milestones is important in PI Planning. What is the impact? The inability to display milestones makes the Now, Next. Later roadmap less usable than other roadmaps Describe your idea I would like to ...
0
Future consideration
9
VOTE
Allow Workspace templates to inherit layouts from product line
Who would benefit? Anyone who wants to use a workspace template for things like automation, but wants to use product line inheritance for layout configuration. Our automations are able to improve data quality and reduce administrative overhead for...
1
Future consideration
2
VOTE
Add ability to turn off sprint velocity calculation in Aha! Develop
What is the challenge? Currently, a Team members' velocity is calculated from the work they have completed in the previous three sprints — and updates after every completed sprint. If they have not yet completed work in a sprint, their velocity is...
0
Future consideration
4
VOTE
15
VOTE
Jira integration user name
In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...
0
Future consideration
2
VOTE
Add ability to report on a features sprint history
What is the challenge? Customers want to track the history of sprint changes on their features so they can see if they are slipping more often than they expect. Aha! offers great reports for showing this sprint by sprint, but the history report wo...
0
Likely to implement
© 2025 Aha! Labs Inc.•All rights reserved