What is the challenge? Making billing changes in advance of subscription renewal requires communicating with Aha! support What is the impact? Since information is not even visible in the user interface, it's confusing. Because the details aren't k...

We lock down our Aha! ideation url to only be accessed from our app. We see that as an important part of keeping our 'secret sauce' secret. The problem is when we promote an idea, our customer get an email with a link that does not allow them to a...

Currently when we have multiple people updating the "Starter Roadmap" we find saving will overwrite previous changes if the previous save has not been explicitly loaded first. It would be nice to support "concurrent" editing and not losing changes...

What is the challenge? On the strategy roadmap, you can only sort epics/feature at the first level (i.e. non-nested). For nested features, the only option would be drag to reorder What is the impact? Manual work to ensure my records are in the rig...

Our data model is such that every workspace in Aha! maps to a platform and we use a custom table to define the mapping. Since the field is mandatory for all objects in said workspace, we make the field mandatory when creating new features. We can'...

Right now if you set the external release date to be the same as the internal release date then the external date moves with the internal date. I would like an option that when you are rounding an external date that it can also update the date to ...

We use Aha! Scores heavily on our features, and while Reviewers can see the aggregate score, they cannot view the values for individual metrics (Sales increase, Retention of customers, etc.). Many of our reviewers are members of our engineering te...

Calculated columns in reports have to use identical Terminology to work properly. Field names in calculated columns calculations are changed by customized Terminology. This means they break if the report is run across workspaces that have differen...

Who would benefit? Teams who need to ensure clear prioritization on the subtasks within a body of work. What impact would it make? Right now, the only way to filter, for example, the features prioritization page to a specific body of work, is usin...

Being able to have a single roadmap line (program epic and feature level) that shows phases (Intake, Discovery, Plan, Backlog, etc) and milestones that are added to the feature