For users sending an idea or feature to Aha! from Slack it would be helpful to be able to optionally include a description from Slack instead of having to open Aha! to add it. The button link that opens the idea or feature is nice, but the ability...

What is the challenge? I'd like to bring a model and positioning exactly as they appear in those respective locations into a dashboard similar to how they can be brought into a presentation. What is the impact? Keeping the model at the forefront o...

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

We use tags on Features and Requirements for grouping items across product lines and between 2 products that connect but are separate applications. We currently use a non-Aha product as a digital whiteboard that allows tags which means double-work...

It would be awesome if we had a way to post messages in the idea portal for users. I'm currently thinking about using this around the holidays to share updated SLA time frames (our portal is internal and we commit to a certain time frame for respo...

What is the challenge? Each of our feature cards have statuses such as Discovery, planning, Design, Development, Test, Launch. There is no way to plot this against a gantt timeline so that it shows a bar for each status with a start/end date. Fo...

What is the challenge? Using this newly developed record, Task, as opposed to abusing the Feature record. Forcing us to add custom Feature > Types for things like "Create Test Plan" which aren't actual features. What is the impact? Usin...

While I can add attachment to an idea from UI and attachments to the comments, I cannot add attachments to an idea from the API.

It should be possible to configure the default selected values of the 'update frequency' to the desired value based on user's usage of the application

The ability to archive Initiatives shouldn't be based on the timeframe value but status. Timeframe can be leveraged by multiple resources, long in range, or not accurately updated. The status reflects a "done" state and is a better indicator if so...