First, I really love the notifications feature. There is just one thing that I wish I could turn off for when I'm presenting or heads down working. As a user, I'd like to be able to turn off the favicon updates. This includes the orange dot as wel...

The use case is that the customer has an ideas workflow where all submitted ideas need to go through a review process before they are actually published to the portal via the visibility settings. What currently displays on the screen upon submitti...

If I use the "Initiative Filter" on the Features > List screen, the initiatives are broken out by Product/Family. But when I use the "initiative Filter" on the Roadmap > Pivot Table view, it shows "all initiatives" in alphabetical order, reg...

Goal: Offer an in-depth class on collaborating with stakeholders using Aha! Class materials Doc templates Whiteboard collaboration and use cases Note collaboration and use cases Meetings

What is the challenge? Need to quickly see and update user permissions based on when they were added (we use SSO - so user records are often created in waves when new teams onboard, but they still need permissions) What is the impact? Saves tons o...

What is the challenge? There are blinding white bars What is the impact? Eye Strain Describe your idea Make them not blinding white bars

Features, Initiatives etc can be mentioned in text in notes, comments etc. But you can't see the mentions when you are looking at the feature. Seeing where features are references would help provide context and a more comprehensive view of the fea...

Would be great to have a visualisation of all feature dependencies within a product. Right now the dependency visualisation exist between features, but that cannot be used to map all feature dependencies within a product.

The ideas portal email updates are great for closing the loop with stakeholders, but some users have complained about the volume of emails they get because of the many statuses we use. I would like to be able to choose what statuses warrant an ema...

We use master features to define use cases that require work from multiple products. The features linked to the master feature come from those different products. However, we need the ability to put requirements on a master feature to be able to t...