Presently, there is not a way for us to remove due dates (or start dates) on epics, etc using the automation functionality native to Aha! We would like to have this as an option in the case that we decide to shelve an epic for a later date we can ...

When creating a scorecard, we'd like to provide a description of the values or attributes within the scorecard. For example, if the attribute is "size", we'd like to be able to say that small means less than 1 week, large is greater than 1 month.

I really want to be able to use the strategic roadmap tool for multiple products, but I can't color concepts by product in this view like I can other reports/roadmaps. The only way to tell which product it is is by the title in light grey parenthe...

The board currently just shows features in a release. Features descriptions are often contextualised by their relationship to an Initiative. Not showing initiatives as grouping of features in a release requires that the feature names carry informa...

When onboading additional team members on to Aha, it is really a pain in the butt to creat 30 accounts by hand. Put a import users option that allows me upload a excel spreadsheet and create those users with the permissions I set for the batch imp...

Hi Aha! Team, Having a filter that ommits certain options would help with reporting.

The cycle is great, but one key element is missing - it's the Product Design phase. I have to put it in "features" or "requirements", but design doesn't work like that. I'm unable to see/ demonstrate the work done by the design team, as there is n...

I would love to have the quadrants of each chart labeled (Sure things, big bets, quick wins, do not do) so it is easier to communicate what we are looking.

We are looking to share a roadmap with external stakeholders from Aha. However, we want to control which external users can access in the case if an employee leaves on of our clients, we do not want them to retain access of our roadmap. Today, the...

Currently Aha stores user first and last names. In the get user and list users REST API response objects, those fields are combined into one field: name. So John and Doe just get returned as John Doe. This causes problems when you have many differ...