The Comments tab available in Ideas, Features, Epics, etc. is vastly helpful for internal communication that's easy to read. Please consider adding the same functionality to Organizations so that users could tag each other and keep a chronological...

This is useful for documenting the support for a completed to-do and show proof why the to-do was considered "complete." These indicators/icons would be useful anywhere a file/mock up can be attached for the same reason i.e. showing proof of your ...

As a product manager managing a release, it would be helpful to be able to see all the to dos and approvals assigned to the phases when looking at the Release Details. This is similar to the idea around having a report (https://big.ideas.aha.io/id...

When we create an epic, and mark that its status is based on features, it should continue to adjust even if the origin feature reached 'ready to ship' and also the epic reached that state, if afterwards we are now adding new features with status u...

What is the challenge? Not able to comment to why a particular linked components are dependent of other one. What is the impact? For certain dependency to be created there are some additional comments required hence we are looking for a comment to...

At the moment you are not able to map every standard or custom field such as Release Name or Original Estimate for Features which would be useful for use to be able to keep records more in sync with Azure DevOPs where the DevOps connector also doe...

Allowing the ability to modify the status of a feature from Slack can be very useful when discussing features with DEV and Product teams to quickly update the move a feature from one status to another

When configuring idea portals, I'm trying to list it in the products in this ideas portal view, can we have a search functional so we don't have to scroll down?

Timeframes are currently treated as strings or labels within Aha!. As a result, ordering timelines will order them alphanumerically rather than chronologically. To a certain extent this can be worked around by specifying the year first and then t...

In the record history, include a link to the automation rule that triggered something to happen so that I can quickly figure out which automation rule caused the change to happen. Currently it can be hard to figure out why something happened when ...