What is the challenge? As a PM, I want to quickly share a feature's related idea portal link with field team to proxy vote (private portal) or customer to directly vote (public portal). Today I have to navigate from the feature to the idea/feedb...

What is the challenge? As new tactical records are being input there are times where new key results are being defined. Today a user would need to go to the objective, then create the key result, then go back to the tactical record and associate...

Ability to track engagement (e.g. number of visits, number of new v. recurring visitors) to our Aha dashboards and reports.

users rarely have cute picture for their user photo when i look at who voted on an idea all i see is the same default user icon repeated many times, it looks like the unabomber voted for an idea 8 times the names are there, but i have to hover ove...

Aha Score is a standard field in Aha and like many others, you still can configure it based on your business requirements. This is why it would be good that the reviewers' users be able to understand the metrics under that score and have quick vis...

When some ideas are submitted to us, the idea comes through with 2 or 3 (or in some cases more!) ideas in it. We have a few custom fields that tie to each submitted idea - so what would be good is if there was a "Split Idea" button which essential...

What is the challenge? Aha! roadmap views etc. embedded in a whiteboard show "Preview is unavailable" when the whiteboard is published in a webpage What is the impact? Improve the sharing and user experience for whiteboard users who are communicat...

We have number of various pages in our Ideas portal where we collect ideas from the rest of the company. In these pages, we aro also maintaining ideas report, FAQs and other Aha! dashboards that we are actively promoting within the company. It wou...

We would like to see multiple heads from the report be viewable in the dashboard view as well. For example, for roadmaps, we would like to see the months, quarters, and year as headers as that is more consumable.

We have users stories mapped to requirements in Aha!. When viewing the capacity planning at a requirement level it uses the feature level start and end date, we want to see the start and end date of the requirement (Story). Also related to this in...