What is the challenge? Currently, the Knowledge Management Views page does not offer a way to export data directly. Additionally, we cannot control how many items are displayed per page. These limitations make it difficult to manage, analyze and...

What is the challenge? Currently we have ranking by literal placement of a record within its board / details and we have ranks from prioritisation views and we have ranks of work in strategic roadmaps. It is extremely difficult to understand con...

What is the challenge? When evaluating themes to determine which ones to prioritize, you might be considering several factors including idea votes, strategy alignment, and org revenue. While this information can be found on (or connected to) a t...

Who would benefit? Portal Administrators and Community What impact would it make? This would allow portal admins to ensure users are only able to vote once per idea rather than multiple times by registering more than one email address and/or corre...

What is the challenge? The existing functionality for showing dependencies in custom roadmaps only works for "depends" but not other relationships What is the impact? If we want to visualise dependencies on custom roadmaps, we can only select eith...

What is the challenge? There is no visibility in Aha! what issue type the Requirement is in Aha!. In addition, we'd like to create Design tasks in Aha! which don't require sync to Jira, whereas we'd like to sync Backlog Items, Activities, and Bugs...

My team has switched from Fogbugz to Linear for ticket tracking. We'd like a two-way sync between Aha features and Linear Issues.

What is the challenge customers want to enter enhancements directly to the product What is the impact? Describe your idea

We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release n...

What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...