We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...

The idea description field in the idea details window does not have a label indicating that it is the description. Is it possible to have a "Description" label appear when the description note field is populated?

We are using work requests to share requirements across workspaces. Since users who will receive work requests must have at least View rights to the sending workspace, it would be useful to know who will receive the request to make sure their righ...

I'm trying to drive standards with my team to enter advanced team-based estimates on all of their work. Right now they have the option to either enter a simple estimate or an advanced estimate. I'd like to enforce team-based estimates by only allo...

What is the challenge? In larger teams that manage all their work on one board, there is a need to look as at the cycle time for a sub group. Currently you can only select the a single person to be shown on the chart. What is the impact? It's not ...

As a user creating (or integrating) a Feature under an Epic, I want to configure if the Feature will inherit the Epic Release, so that I can automate my Release scope when I create (or integrate from JIRA) a new Feature in an Epic. This will help ...

As product management, i need to see project, features, todo's and idea based on their status. Filtering by status helps reduce the noise of stuff assigned to me. To me, filtering should be enabled for all available fields just like most Aha views.

When promoting an idea to a new record, the dependency linkages get carried over from the Idea to the new record. However, when promoting to an existing record, this does not happen. We rely on this carry over so that PMs do not have to do extra m...

The number of idea subscribers is an attribute within an idea detail drawer but it cannot be included as an attribute (or column) in the Reports area of Aha!. This would be useful so that the total number of subscribers column can be sorted agains...

Currently there is a 10 vote per idea cap. It would be nice to be able to allow a user to use all their available votes on one idea. This would allow the user to show that out of all the ideas, a single idea is the most important feature for them....