All ideas
Sort by:
Trending
Status:
Unlikely to implement
Showing 9227
5
VOTE
Delete in Aha restricted to Admins expand to Custom roles
What is the challenge? Recently Aha! implemented a feature for restricting delete but once enabled only Admins can delete records. What is the impact? We have some power users who required delete permissions but do not need other admin priviliges ...
0
Future consideration
5
VOTE
Allow changing integration template when project is not based on template
What is the challenge? A new integration template can only be applied if the projects for the new and old template match or if the project matches the existing integration. What is the impact? There are scenarios where a new template needs to be a...
0
Likely to implement
1
VOTE
Retrospective Report - Not all releases are displayed
What is the challenge? Releases are only available for retrospective if a feature thats is connected to the release moves to "in progress". Since some of the releases contains epics only, such releases are not made available for retrospective. Wha...
0
Future consideration
1
VOTE
Allow to manually push a Jira Theme to Aha as an MF ( without the need of a ready MF on Aha side)
What is the challenge? Currently we have cases where RnD would open a theme (we categorize it) , and that is for mostly themes with technical nature. as such PM will not initiate them, but we still want the PM to be aware of them in planning and p...
0
Future consideration
3
VOTE
When adding a report/roadmap to a dashboard, default to not making a copy
What is the challenge? When working with users to build Aha! dashboards, many do not intend to make a copy of the report they are using for their dashboard. However when building the dashboard, it default sets it to make a copy and this leads to a...
0
Future consideration
3
VOTE
Create a new field type to make establishing relationships to records more consistent
What is the challenge? Today teams can create any relationship between any record through record links. As standards are established some teams would like the ability to ensure specific relationships are set between set record types. What is the i...
0
Future consideration
8
VOTE
Do not automatically create record links when records are mentioned
What is the challenge? Users capture important details about an epic or feature in the description of the record, which is a note-type field. In some cases, the user needs to mention another record and does so using the "#" mention. Today, the men...
0
Future consideration
5
VOTE
Disallow linking with already integrated record
What is the challenge? Our organization has strict reporting coming out of Aha! that requires records to only be connected with 1 record in downstream systems (Jira in our case). Aha! currently allows you to intentionally link multiple Aha! record...
0
Future consideration
5
VOTE
Allow To-Dos, Approvals & Work Requests to all be pulled in as one object in reporting module
What is the challenge? Today, when reporting on To-Dos, you need to pull in three different objects to get To-Dos, Approvals & Work Requests in a report view. This will put all three of these items on the same line in list views and pivot view...
0
Future consideration
2
VOTE
Improve Epic (Feature) Prioritization page to allow key results to appear as a column
What is the challenge? Teams today associate key results to Epics (you may call them features) and objectives to Programs (you may call them Programs) but are unable to view their key results as a contextual column in the epic prioritization view....
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved