What is the challenge?
When reviewing and analyzing interviews, I want to clip moments from interviews so I can easily share then with my team and stakeholders. It is not easy to share a section of the video where a customer describes the challe...
Related information shall offer customizing option
What is the challenge?
Currently on related tab not very section does offer the option to view information in report (ie People also voted for)
currently the columns with information displayed do not offer option to add a column of information...
Sue Schneider
6 months ago
in Ideas
0
Future consideration
Improve the UX for attaching files to support requests
What is the challenge? Clicking "Attach files" in the Get help from an expert > Email support, replaces any previously attached files.
What is the impact? Confusing experience when attaching multiple files:
The form accepts multiple files, b...
Ben Hollier
6 months ago
in Application
0
Future consideration
Automation of feature to another release based on custom field
Who would benefit? Product Management Team What impact would it make? Ability to cut down on manual work, reducing mistakes and time spent on administrative work How should it work? Under automations, be able to set a rule as such: When a feature ...
Danielle Martinez
almost 3 years ago
in Automations
3
Future consideration
What is the challenge?
We would like improvements to Aha! automation to make it more scalable and efficient across workspaces.
1. Bulk Automation Management Allow bulk select and move/copy of automation rules across workspaces to reduce manual ...
Prachi D
8 months ago
in Automations
0
Future consideration
Unclear where to type & paste interview notes in Aha! Discovery
What is the challenge?
It is hard to spot the section where you can quickly type or paste your interview notes within Aha! Discovery
What is the impact?
This causes confusion and slows users down
Describe your idea
Make it clearer wh...
Chris Quigley
8 months ago
in Discovery
0
Future consideration
Delivery Risks - Ability to Inherent to Child Workspace
What is the challenge? If one product line (parent workspace) wants to implement Delivery Risks, we would need to individually go through the settings on each child workspace to configure. What is the impact? It is very time consuming for large pr...
Manny Pannu
over 2 years ago
in Settings
2
Future consideration
What is the challenge? Roadmap reporting lacks a unified way to apply and manage filters across different report levels. As users move from a high‑level roadmap view to more detailed information, there is no guaranteed consistency in how filtering...
Ashton Tsou
6 months ago
in Roadmaps
0
Future consideration
Allow drill down into 'Related' records on Presentations and Webpage share
We attach a lot of ideas and/or features to epics, initiatives, and goals. That level of granularity is not needed in the presentation itself or the initial webpage view, in which we display only high level planning objects (initiatives, epics, go...
Enhance the Audit History API to provide complete user information for both custom User-type fields and system User-type fields. For custom User-type fields, in addition to the existing raw_value (user IDs), expose the corresponding user email addresses (similar to the email_value field returned by the entity retrieval APIs). This would eliminate the need for additional user lookup API calls and keep the Audit History API consistent with the entity retrieval APIs. For system User-type fields (such as Assigned To, Created By, etc.), enhance the Audit History API to expose the underlying user identifiers and email addresses, rather than only the display names. Providing user IDs and email values would enable reliable processing of audit records, avoid ambiguities caused by duplicate display names, and offer a consistent experience across all User-type fields. These enhancements would improve API consistency, reduce integration complexity, and make audit history processing more reliable for customers integrating with Aha!.
What is the challenge? The Audit History API currently provides limited information for User-type fields. For custom User-type fields, it exposes only the user IDs (raw_value) without the corresponding email addresses. For system User-type fields ...
Allow attachments to Feature comments to be integrated to Azure DevOps
When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...