Currently you can color by status on the gantt chart to see the release phase colors appear. It would be helpful to include the release phase colors on list and pivot reports as well.

Who would benefit? External stakeholders accessing published views of reports What impact would it make? Ensure security of webpages published views if screen grabbed How should it work? In the 'share as webpage' dialog add ability to upload JPEG/...

In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...

We would like to be able to 'lock down' some fields unless there is approval to change them. For example, Release date (or due date) Budget Designated people in the company would be required to approve any changes to these fields. Along with this,...

Currently, there's not a streamlined way for features to inherit their goals from initiatives as it requires many automation rules. Recently an enhancement was made to allow features to inherit their goals from the epic. It would be ideal if a sim...

Who would benefit? Sales Engineers / Implementation Managers who want to apply additional documentation on behalf of customers to an internal idea portal What impact would it make? One less touchpoint that a PM has to make to get this documentatio...

Who would benefit? Aha Notebooks users What impact would it make? Increase storytelling ability when using whiteboards by providing the ability to add in icons/images to flesh out an idea beyond words How should it work? See attached screenshots f...

The color of the toggle CTAs for Master Features (Epics) and Features are different shades of gray, which makes it hard to determine which is currently active. Typically, gray is used to indicate when something is not available. Differentiating li...

When SSO is enabled, there should be an option to disable the "New User" tab on "Add User" screen. This would reduce some confusion on how users get access (they just need to sign in vs. being invited/registering).

Would like a way to have the timeline for capabilities without a start/end date (aka, sitting in a parking lot) to not span an entire timeline. As it is, it looks more like it’s something that is going to take a long time, versus something that is...