Hello, we are working at this moment from Calendar view, with a number of features per day. That works great for features requiring less than a day to get finished. But to plan on larger features, it shoud be nice to have a planning system on top ...

Currently, when you send an Epic to Jira, all of its features are sent, but they are sent as the default Feature type instead of the types that they were actually categorized. Often the product person is working in Aha! and doesn't want to yet sen...

Need ability to keep initiatives and goals accessible for reporting - especially as we cross over years; but, need to keep folks from using them. It seems if we keep them from using them we can report on them which is the problem we are needing to...

Admins need to be able to see and edit all reports. All too often, someone may leave or not available and a report needs to be updated; however, because the original owner restricted it to be view only, we end up creating another report in order t...

We are trying to create a custom scorecard to help with next year's planning. We need to socialized the formula, the weights and what the scores mean. I'd like a way to download the scorecard creation screen to a PDF or a CSV--or just a better vie...

We are getting duplicate contacts created in Aha, and have a need to consolidate their votes, without causing the overall org vote count to increase. This affects our reporting on org votes, and impacts our vote count on ideas.

When I export an Aha! Note to PDF, the note icon is included in the PDF export. I would like to remove that icon as it does not look desirable on a professional document.

In Aha, it's difficult to represent the relative effort required for different master features and features. Time is not the only consideration. For example, so features have dependencies that while not requiring heavy effort, will effect the dura...

It would be really useful to be able to list/count the total number of objects (requirements, features, master features, releases, initiatives, goals) across one or more products in a single pivot report. This could be done by making a product in ...

Being able to show the configuration across workspaces in a report is extremely valuable. The Record Dates configuration is not an attribute that can be reported on at this moment in time but would be useful as currently it can only be seen by goi...