What is the challenge? Today, Themes cannot be automatically assigned to Ideas based on predefined logic (e.g., Category, tags, or other fields). This requires manual effort to link Ideas to strategic Themes, which is not scalable as our products ...

What is the challenge? Our organization does not use Version per workspace. We have a centralized release process and use a custom field to identify Epics/Features target to release. What is the impact? the Board view is not used as it should be ...

I would really like to see additional styling options on the Roadmap reports within Aha! Settings for the Custom Roadmap gives Bar View and Bar Size exist already but I would love to see the following: Custom gradients / patterns for the Gannt Ba...

It would be helpful that the set coloring chosen for a specific feature tag remain consistent when displayed in reports or charts. Currently, the coloring when including feature tags into a chart seems to be random and can cause confusion when mul...

I want to understand more about the records that are added to or removed from a release: When was it removed? Where was it moved to? What is its current status? I would like to see this information in the retrospective report

It would be helpful to be able to add the same comment to multiple ideas at once. I use this to record when I have sent a group of ideas to a group or have done the same update to multiple ideas.

Today, if the detailed estimate is 0 then the Initial estimate is ignored in the best estimate calculation. I would expect us to ignore null/zero detailed estimate values if the initial estimate is >=1 when calculating the best estimate.

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), each i...

What is the challenge? We use the 'Note' field throughout our record types, including Goals, Initiatives, Features, Requirements, etc. While we can use To-Dos, it would be easier for many of our use cases to @mention someone directly in the field ...

Once we have created a release and scoped all the items into it, it would be helpful if we could "soft lock" the features in that release. A soft lock could be an option on each release with a toggle and a message. Once the toggle is ON and a new ...