All ideas
Sort by:
Trending
Status:
Planning to implement
Showing 20
6
VOTE
Allow removing "Success metric" from View layout on Goals when OKRs are enabled
When OKRs are enabled in a workspace, it is possible to fully remove the "Success metric" field from the Create version of a Goals layout. On the View layout, that field can be hidden, but cannot be removed entirely. This should be possible so the...
0
Planning to implement
3
VOTE
Placeholder text in a custom note field should appear as formatted in an idea submission form
What is the challenge? Currently, if you add placeholder text with text formatting (such as colour) to a custom notes field, this appears differently when viewed in an idea submission form. This includes text colours and line spacing What is the i...
0
Planning to implement
6
VOTE
Ability to track key results values over time
What is the challenge? When OKRs are enabled, there are 3 fields to track: Target metric Starting metric Current metric However, there is no ability to track changes to these values over time. The need is highest for the "Current metric" field. Wh...
0
Planning to implement
3
VOTE
OneDrive Integration is not currently allowing files to be attached to Aha! Records
What is the challenge? OneDrive Integration is not currently allowing files to be attached to Aha! Records What is the impact? Users are unable to add files from their OneDrive as part of the integration, so they have to find other ways to upload ...
0
Planning to implement
5
VOTE
Add true "Detailed estimate" option to release retrospective report
There is a current option on the Release Retrospective Report to view "Work completed (points)" which displays records associated with the release and totals with the "best estimate", using the initial estimate unless a detailed estimate is availa...
0
Planning to implement
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
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
20
VOTE
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
© 2025 Aha! Labs Inc.•All rights reserved