when I use the "Initiative Filter" on the feature list board, it shows all the possible initiatives but I'm usually working "within" one product or another, and most of the initiatives will never be relevant (only the ones for a product or product...

As an admin, we are addressing logging and monitoring policies in our company. We would like to capture a log of API calls made to a specific Aha instance. We are aware that you have an activity webhook that will notify our system of every change ...

What is the challenge? Users are allowed to promote an idea at any stage of Ideas workflow What is the impact? Risk of promoting an un-approved Idea, will lead to unapproved roadmap item Describe your idea An idea should only be allowed to 'Promot...

The Parking Lot needs beefing up. If you have a lot of granularity to your Parking Lots (created Parking Lot A, Parking Lot B, ... Parking Lot Z) it gets hard to us UX wise. The gray expandable box on the Board view resulting in lots of scrolling....

We have started to dip our toes into the capacity planning in Aha by doing initial estimates and looking at resource allocations over certain time frames. It works great. However when we turned on capacity planning it also meant that a capacity li...

What is the challenge? Working out who is Owner and Contributors across all Workspaces and Lines in order to be able to review whether additional seat needed What is the impact? Makes it so much harder to manage Describe your idea Mu...

Who would benefit? Any client, but especially those practicing SAFe What impact would it make? Make it very clear which features can be pulled into a PI and which won't, based on capacity, so negotiations can commence! How should it work? On the C...

We use the initial estimate field for early product planning. While the "No detailed estimate" field helps for our detailed planning stage, we want similar functionality that checks for missing initial estimates to support our earlier planning.

The release retro report currently uses only a single (pseudo) milestone: when development started. Some teams want to measure changes in the release relative to several milestones within a release, such as a beta launch, or code freeze.

When reviewing an active release via the release retrospective report, I want to see the current status of incomplete features so I have a better sense of how close to completion they are.