All ideas

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 using the Chart view to map ideas to the Value/Impact matrix, it looks like the list of ideas to be charted is sorted alphabetically. Would be more useful if this could be sorted based on number of votes so we can review the more popular idea...

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)

As a Release Manager, I can show releases in the order in which they will occur. Today, they are ordered left-to-right by their external release date but since we cannot specify a release time they tend to show in the wrong order. There are instan...

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

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!

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