Application

We use automation emails to notify PMs and a few others anytime a new idea is posted. These contain no information beyond the name of the idea and a link. As an Aha admin, I want the ability to select the specific fields I want to include in autom...

Users are really struggling with reports and roadmaps. They want to be able to find what they are looking for with just a couple of clicks and are overwhelmed with all the options presented to them under Roadmaps - as they have no idea what a pivo...

Product Integrations are set-up by a system admin to run through a webhook. We used an Automated User account to set up the webhooks so it's not attributed to anyone specific but the feedback we get from users is that of frustration. PMs want to s...

What is the challenge? We would like to use Knowledgebase Advanced to track things like User Documentation, FAQs, and Release Notes and make this available publicly. However we need a way to disseminate this information to our users who have want ...

Currently only Aha! Users and Reviewers can add Ideas via Slack integration. Non-Users/Reviewers have always been able to submit ideas via the web portal so extending that as part of Slack -> Aha! seems like a next step. Our users would like t...

What is the challenge? Currently you can set the fonts "Inter" or "Ret Hat" in your knowledge base, not but in an Aha! note What is the impact? Confusion over supported fonts/the inability to visualize the knowledge base font within Aha! ...

What is the challenge? Currently a study can only have one script. Interviewing different user types/personas can often require a different interview structure with persona-specific questions. Currently, this has to be built into a single script...

Aha! contains some incredible reporting capabilities that allow anyone to quickly create and share reports associated with the development activities. This is incredibly convenient and helpful to share information in a transparent way and empower ...

What is the challenge? Currently, the Team fields do not display on Requirement records if the parent Feature is a Develop/Teamwork Parking Lot feature; however it does display on the Feature's Requirements if the record is assigned to the Team ...

Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...