Annoying maintenance task of updating expired webhooks that keep making systems out of sync and we end up using VSTS as the source of truth rather than Aha!

We want to use the upper levels to be our Hopper of personas that are managed by our design team. But we don't want users to be able to edit these unless they have Product Owner permission at that higher level. The idea is that when a product mana...

We want to automate the user provisioning and make sure we don’t provision users beyond the allocated count. Hence we want to leverage API to get the allocated user count .

It'd be really great to be able to see all outgoing emails that are sent along with a delivery/viewed status. This would allow us to better support our customers by seeing/ensuring they receive our notifications and in allowing us to audit exactl...

Since Bugs are not 'first class' entities in Aha and the suggested workaround is to map requirements with bugs in JIRA, we have done that and use a custom field of type in requirements which has the value of bug and story. However, when we open a ...

Ability to have the Aha notes sync to Teams Wiki

It would be more intuitive to be able to delete To-Do's from the view you see them in, instead of needing to go into detail view to delete each specific one.

In the board view for Features, you can pivot between epics and features. I would like to be able to see a view where epics are on the left and features are on the right, enabling simple drag and drop of features into an epic. We often start off w...

It's helpful to be able to measure the complexity / effort of work compared to the value we expect it to bring to our users. While setting this for initiatives is useful, we also need to be able to do that for Epics and Features.

We use the idea board to gain insight into our customer needs. The sizes of our customer vary widely and when the larger companies submit an idea, they send an internal blast to their users to vote on the idea. This skews the data and makes it dif...