In addition to the existing statuses (Pending, Overdue, Complete), I would like a new status called Not Required. Currently we annotate the To Do title with n/a - however it would be easier to have this as a status as this would aid with reporting.

In our organization, we have delegated users who are responsible for assisting in setting up users in our idea portals. Today, in Aha, that requires the user be a full administrator able to manage product lines, billing, etc. It would be very usef...

We are using a custom field to store a table structure of data. We find that the right panel is too narrow to show our data in a readable format. We'd love to be able to expand the right panel horizontally. Or we could solve this problem if we had...

1) Take a release with 4-5 features 2) On a gantt roadmap, reorganize (sort) the features differently 3) As a different user, view the gantt chart The order of the features are not the same between both users and becoming annoying.

In Integration, I am not able to choose which statuses I send and which status changes I do not. Example, captured, i do not want to send, but Aha Integration allows me to send to down stream systems with a blank mapping. Please enhance integratio...

we are in the process of switching over to Swiftkanban as the kanban board is great to use and allows us to create end to end workflow. We will more than likely continue to use AHA for strategy but ideally we are looking for a single solution that...

It would be useful to be able to use the "Integration" as a filter option for feature views. For example, I coordinate a project across three different teams, each with their own integrated project outside Aha! This would help me to separate their...

Currently I can create a link in the Aha! text editor by selecting text, the clicking the link icon and entering the URL. It would be great if I could just select the text in the editor and paste the URL to automatically transform the selected tex...

Much like any omni-channel heldesk tool, the Aha platform allows for a variety of ways to submit an idea - be it manually from within Aha, bulk upload, via email, a chat bot, multiple portals, account specific portal, zendesk/sfdc/jira/uservoice, ...

It would be useful if Aha would add a "grouping" capability for Features, while that grouping must not be related to any particular Release. Eg. for one product I do have today ~400 features in planning and backlog. They are spread out across 3 di...