Currently, to pront a report you need to click the "up arrow" -> select "pdf" and only there you can choose the print option. why not just add the print option directly on the drop down list from the "up arrow" (similar to iOS options...

I really like the new UI, but there are a few things I do regularly that seem to take more time now. The one that is the most annoying is having to select 'Saved Views', then wait for the modal to load and then choose the view I want to work /with...

The customer success team suggested I just use initiatives for user journeys and master features for user journey steps, which is a good temporary fix. However, defining a user journey is a pretty specific thing that I think should be set apart fr...

In program reviews, it is incredibly helpful to be able to surface up changes on initiatives from previous meeting. Being able to have a change date like what features have would enable to provide a report or view of initiatives that have dropped ...

Aha! provides a great functionality to change terminology in the idea portal, but it is not reflected back into Aha! idea functionality. Example. You can change 'Votes' to 'Likes'. The portal reflects the changes. The Aha! UI for ideas still say...

When creating a starter roadmap I like to drag and drop new features into release. If two features have the same start date they should auto vertically stack otherwise a user won’t see the feature below the other one.

When we review and check "Need More Information", Aha should automatically send a "need more information" message to submitter. Then it will automatically remind the submitter for 3 times once each week and then send a "closing" message due to lac...

Currently, when you create a report (or pivot), the field names in the Calculated fields are based on the workspace selected when the report is run. Even if you provide a user a link to a report and they open it, the system defaults them to the wo...

Provide more precise control of timelines by linking requirement due dates to their associated Feature's due dates.

When we create features, there is not a validation message of the newly created feature (preferably including a link to it). We just see the button "saving" and then stopping. The idea is to give more feedback to the user that a feature was create...