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...

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.

What is the challenge? The standard Salesforce Opportunity report uses the default opportunity value, not our custom USD-converted field. What is the impact? This makes the built-in charts and cards inaccurate for teams that rely on normalized US...

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 ...

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.

What is the challenge? Our organization has strict reporting coming out of Aha! that requires records to only be connected with 1 record in downstream systems (Jira in our case). Aha! currently allows you to intentionally link multiple Aha! record...

What is the challenge? When integrating with external tools like ChatGPT, creating or modifying records one-by-one requires constant context switching by the AI. They cannot loop through 30 requests like a script might. As a result the AI consta...

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? Today, when reporting on To-Dos, you need to pull in three different objects to get To-Dos, Approvals & Work Requests in a report view. This will put all three of these items on the same line in list views and pivot view...

Who would benefit? Any user who is using the Now, Next, Later roadmap and defines their timeframes by quarter. What impact would it make? This would enable additional flexibility for more 'ambiguous' timeframes (i.e Next) How should it work? Allow...