A more detailed Capacity Planning feature would allow us to better manage our roadmaps from the perspective of what is achievable based on our current resource levels. The following high level features would be included in a more robust capacity p...

Mobility is key to making a tool universally accepted in the workflow of a team. Look at the popularity of Slack as a result of the user experience of using the product across multiple platforms/devices. It would be great to have the core team fu...

I would love to be able to add a blank slide to a notebook that allows me to upload a picture or format some text. Similar to a title slide but able to be placed anywhere in a notebook. These would really help us to setup sections in notebooks.

I would like to be able to have a user story mapping tool added to aha. This is useful in that it enables us to see what a priority of a release would be and what is a minimum viable product versus what would be added to a later sprint. This would...

I would like the ability to choose how my feature statuses map to idea statuses so when feature statuses change, that I have mapped to an Idea status, the idea status also changes (and changes in status notify subscribers of ideas).

It would be an improvement to be able to define the fields that appear when creating a request. For example, I have added a custom field to tag the customers that have requested a feature. Currently I have to add a feature, then edit the field in ...

Would be great if Aha was mobile friendly. That way we can log time, update our notebooks, see what we are working on in a current sprint etc on the go.

It would be great to be able to define in Aha! what "company" or "account" each Ideas Portal user belongs to. After the company information is available, we would then want the ability to filter and sort the Manager Portal Users screen by this fie...

Given "Aha! is for the "why" and "what" and JIRA is for the "how."; Master Features are useless unless we can implement them alongside JIRA.