Who would benefit? Any customer who has a quarterly marketing release that impacts multiple products What impact would it make? this would allow us to have a single consolidated view across our products with a single reporting view so the entire b...

Calculated columns in reports have to use identical Terminology to work properly. Field names in calculated columns calculations are changed by customized Terminology. This means they break if the report is run across workspaces that have differen...

When using filters in Features, Releases, or Roadmaps, dynamically show options that are relevant to what has been filtered. This is already implemented when using a workspaces filter and a specific workspace or group of workspaces is selected. Th...

I'm not sure why it's not possible to have features in release templates. Phases and milestones are nice, but features are what actually have the status. This would be especially powerful for recurring releases. For example, I'm manually creating ...

Being able to have a single roadmap line (program epic and feature level) that shows phases (Intake, Discovery, Plan, Backlog, etc) and milestones that are added to the feature

When user logs out of Aha! the logout message should be sent to the IdP. If user logs out of IdP Aha! should process logout message and also logout user. This should be supported for both Aha! and for idea portals.

What is the challenge? Large programs with lots of features in motion, it can be hard to spot if a feature has stalled. What is the impact? We don't have enough time to react properly and help the stalled feature in a more proactive way. Describe ...

As I work through the requirements on a large feature, I find it useful to keep them sorted by status, so I can have a focused group of items that still need my attention. It would be nice to automate this sorting via a rerank button, similar to t...

Similar feature to Outlook overlay with the tabs – this would be epic for yearly planning to ensure sales enablement activities and releases are coordinated effectively.

Our data model is such that every workspace in Aha! maps to a platform and we use a custom table to define the mapping. Since the field is mandatory for all objects in said workspace, we make the field mandatory when creating new features. We can'...