Delivery

What is the challenge? A way to consistently gather usability feedback from users What is the impact? Users share usability challenges in email, IMs or sometimes in meetings (Data is inconsistent) Describe your idea A feature that ca...

What is the challenge? The marketing team is moving into Aha! Teamwork. For the most part we are planning to visualize work at the requirements level. We love that you can add icons and color activity cards by type. But unfortunately we do not ...

Currently if I select a new workflow for my team and map my statuses to new statuses, I lose all past cycle time data because cycle time only focuses on the current workflow being used. Instead, I would like to see historical data that coincides w...

Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...

I would like a retrospective report for program increments. I want to see the following when a program increment is completed: PI burndown and burnup reports Features added after starting the PI, features removed from the PI after starting Average...

It would be beneficial for the Product team to be able to share a view of initiatives in the workflow as it's the right level of information. The view can be added to a presentation but I'd love to share just a single page that folks can click to ...

Hi Team, is there a way to search the Team Board like you can in the roadmaps workspace, I see the search feature in the sidebar for backlog but not on the team workspace.

If the workspace status of a feature/record is set to 'will not implement' then ideally it should be removed from the workflow board in Develop too.

When using Aha! Develop to track bugs I want to see specific fields that are only relevant for a Bug record. EX. Severity, date raised, reproduction steps etc. So that I can report on this specific subset of record types and their progress without...

Our development workflow has many granular states, like "Ready for testing", "Testing in progress", and "Testing failed." With this granularity, we don't have to ask developers about where the feature is – the status gives us enough information. H...