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 ...

When I see that someone has "completed your to-do" or "commented on your to-do", I would like to see the associated comment they made when adding info or marking the To-Do as "done". This would allow me to delete the email and take no further acti...

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)

It would be a great improvement to add some required questions to the idea form so we can gather the right data up front from the person submitting the idea. IE: Customer Use Case, Impacts Who, How Important?

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 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 ...

Annoying maintenance task of updating expired webhooks that keep making systems out of sync and we end up using VSTS as the source of truth rather than Aha!

In tag fields, trigger the list view of tags only after clicking within the field. If I need another tag, let me click the field again. Currently, the behavior assumes that if I choose one tag, I'll probably want more. I don't, but I have to click...

Since Bugs are not 'first class' entities in Aha and the suggested workaround is to map requirements with bugs in JIRA, we have done that and use a custom field of type in requirements which has the value of bug and story. However, when we open a ...