Aha is the only real all-in-one business/product planning tool on the market & is incredibly powerful & flexible... However, it's not the easiest tool to use by far. I think it would be helpful for the Aha team to take a step back at this ...

When I'm using the features roadmap, the filter setting for auto-updating to include all releases in a workspace doesn't work if any of the releases in that workspace roll up to a release in a product line above the workspace. Instead, I have to m...

When worksheet fields are used in a formula, the text in the 'name' is used for that purpose as part of the syntax. Sometimes, it becomes necessary to change the name and that also means we have to change the formula wherever it is used. If there ...

We use the roll-up initiative feature a lot at the line level and the initiatives at the product level. So all the features and master featured are linked to the initiatives but when we look at the roll-up initiatives, we are not able to see them ...

As a user, I need to be able to see the progression of date changes. I am unable to easily track changes to a specific field. I would like to be able to filter my history of an initiative to a specific event, such as End Date change.

Currently the Gantt chart (and all auto end date calculations) assume release phases cannot be worked on over the weekend. This is not always the truth (we're using a 3rd party to QA our builds over the weekend)

We’ve got users landing on pages that have been disabled on their main menu when they navigate between workspaces. This causes some issues when rolling out Aha widely as an ‘intuitive’ self serviceable tool. An example is: Going to a workspace def...

We can use Customize Style to change the colours of bars in Custom Roadmaps, but this requires us to individually set the colour for each item. This is painful when you have multiple roadmap reports and are trying to keep things consistent. In my ...

With the current configurations, when a user submits an intake ticket to digcharter.com and replies to the autogenerated email, a new ticket is created. This leads to confusion where we might be updating comments on 1 ticket but then realize later...

We use notes to capture information related to the EPIC. While there are other custom fields that can be added natively to an EPICS's layout Notes is not one. The only way I've seen to attach a NOTE to an EPIC is making it RELATED. The issue with ...