We have 20+ people in Contributor role working on the same Product. All of them have by design access to bulk actions and can inadvertably bulk delete all of the hundreds of items that we have in Aha!. We want to somehow restrict access to bulk ac...

This benefits developers who would like to increase the functionality of Aha! applications, which in turn benefits all the Aha users at large by making everyone more productive! Currently, the Aha! API User endpoints that return product_ids gives ...

A large part oft he PO process is creating Wireframes, Mockups, and Prototypes of software. The PO can often times work very closely with a UX team to create prototypes to get a project greenlit. There are many UX tools but JustInMind has become o...

As a user planning a release, I want to have my release phases overlapping finish-to-finish with a lag time defined so the dependencies maintain the overlap that is initially set with the dependency so that I can more realistically represent the o...

CAPACITY PLANNING/TRACKING/REVIEW There is a very frustrating situation when capacity planning done in the beginning of the release can not be persisted by the end of the release when you have undelivered features and have to move them to another ...

This is mostly for the purpose of emails, but when I change the status of an idea, I usually have a comment to add too. The followers get two subsequent emails but it really should be just one.

When bulk edit product permission to viewer or product owner for example, product line permission of "none user" will change to the new value accordingly while other users will keep their their individually assigned permissions. This is ...

We use EPIC tags to filter EPICs, which are filtered to generate PDF exports, however, one EPIC can have multiple tags associated with it. It would be great if we could enable the tags to show, but only show those tags which match the filtering cr...

We share our Roadmap by Release Phases - not the holistic Release - so it would really be helpful to have Internal & External Release Dates by Release Phase.

For users who have more than 1 email address it would be useful to have 1 user associated with multiple email addresses.