What is the challenge? Today, the Jira integration supports movement of integrated records across Jira projects via use of an integration template. However, if the integration includes sprint mapping, a board must be selected in the template. Th...

What is the challenge? Large volumes of customer feedback is often spread across many external systems (surveys, in‑product feedback, support tools, data warehouses, etc.). Today Aha! AI can only reason over data that is stored in Aha!, so feedb...

What is the challenge? When migrating to Aha! Whiteboards, you often have existing boards that you want to quickly reproduce in Aha! — whether they are stored in another tool or captured in a non-digital format (such as sticky notes on a wall). ...

What is the challenge? Currently, the 'Team members' count on a Work Schedule includes deactivated users. What is the impact? The counts can appear misleading because they include users who are no longer active. Describe your idea Re...

What is the challenge? User story maps only work with certain record types and you can't change how the cards look. This makes it hard for teams who organize their work differently. For example, our team tracks user stories as requirements inste...

What is the challenge? Need to update existing releases with language that was refreshed in a Template. What is the impact? We use 10 different Templates and have about 100 Releases in progress, which makes the copy-paste troublesome. ...

What is the challenge? Currently, can add custom tab and name them as we want. We want rename the Overview tab e.g. to Status - currently cant do this which is causing confusion. What is the impact? End user confusion Describe your ide...

What is the challenge? Other Aha users are undoubtedly creating agents, requests and instructions that can add value to the Aha community What is the impact? Expanding the Aha community and quickly growing prompts that assist all users, no...

When creating new issues in GitHub, an "issue template" can be applied. It's not possible today to specify an issue template when sending an Aha! record to be created as a new issue in GitHub. This is problematic if we also need to send the record...

What is the challenge? Unable to see the usage data for a use accurately and for time period. What is the impact? Currently it shows data since the account was opened. Unable to assess if the user had not been using Aha much in the last 3 ...