Teams need to compare the built-in Assigned to field with one or more custom Users fields directly inside list report calculation columns. Today there is no supported native way to create a calculated column that reliably identifies a mismatch bet...

What is the challenge? We can filter on 'show all votes' (proxy votes and customer votes), 'only show proxy votes', or 'only show votes linked to opportunities'. This is missing the option for 'only show customer votes' if I want an easy way to se...

What is the challenge? If you have a fixed workflow and you navigate to the epics/features workflow board, users can create new records at statuses further along in the workflow. What is the impact? This allows them to create records without goin...

What is the challenge? We have certain fields that we use to collect updates (for example, to RAG status), which we're using a note field for. We want to keep a record of previous updates, but enable easy reading of the field, especially in report...

What is the challenge? The "time in status" fields for a Team workflow are not available for records that have both a Workspace (Roadmaps) and Team (Teamwork) workflows. These records only have reporting available for the Workspace statuses/workfl...

What is the challenge? When creating a record via the MCP connection and record pills are in the description, those records are not showing on the Related tab automatically. What is the impact? This is requiring an extra step and inconsistent beha...

Currently swimlanes are by owner which is helpful when micro-managing resources however we group resources into teams and focus features on given teams. It would be nice to support custom fields/groupings on the swimlanes so I could choose how i w...

Many intiatives may benefit from some common functionality. If you could add a feature to multiple initiatives it would allow you to better track the impact of the feature across the entire business.

It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...

We build spec‑driven integrations against the Aha! REST API (OpenAPI codegen, LLM tool frameworks). These clients can only send parameters the published openapi.json​ declares. The gap is API‑wide, not endpoint‑specific: the spec omits query param...