Who would benefit? Reports for auditing purposes What impact would it make? Allow custom functions to flag "is null" for multi-select fields that don't contain data. Currently unable to build custom functions for this type of field. How should it ...

We would like to be able to hide and un-hide the Description and Contact fields on the epic level. A plus or minus sign that closes or expands the section would be perfect. In the new view, the rows are taller and columns wider, which requires mor...

In Excel or airtable, I can create an equation that allows me to sum or run other operations on a series of data that may include null values. Those null values are simply skipped. In Aha! if any field I use contains a null value, the entire equat...

Yes, we can do this in the portal but sometimes when you are on the go and have a few minutes to review ideas, it is good to immediately be able to slot them in as features in future releases.

Currently anytime someone clicks into and selects text from a note, those watching the note get notified that the note was updated, when in reality all that happened was someone highlighted and copied text out of it. This gives a lot of false posi...

IT would be great to have an undo or recycling bin for ignore integrations. It's happened on multiple occasions where someone accidently has one checked that they didn't mean to ignore. Along these lines, it would be nice to have an undo button fo...

Who would benefit? People who support the implementation of Aha! across an enterprise, and anyone trying to find multiple presentations What impact would it make? It would save time, clicks and make it much easier to manage the proliferation of re...

Currently, selecting a new scorecard will erase all existing scores. The manual workaround is to export all your scores and re-import them again after changing the scorecard, but this is very tedious and non-obvious. Instead, allow the user to map...

It would be helpful to be able to view 'Features' within an 'Epic' in the same way we view 'Requirements' within a 'Feature'; as list with similar functions such as reordering, expanding, etc.

Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...