It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...

What is the challenge? The prioritization report cannot display strategy fields tied to multiple records (like goals, objectives, and key results). What is the impact? Goals, objectives and key results are vital reference points when determining a...

Accessing features and other items from a report is useful, but when it's shared as part of a presentation, that functionality is lost. It would be great to present and share data in a report that we've crafted and continue to allow them to refere...

What is the challenge? Studies are a critical construct in how Discovery users organize and manage their work, but the capabilities are limited to fully manage research projects. What is the impact? Discovery users needing to better manage...

What is the challenge? just a missing component What is the impact? no one knows how a feature is allocated when reviewing the roadmap Describe your idea Just make type available to add to the card

Our company is looking to adopt WorkBoard as our corporate standard for OKRs. Our development business units use Aha to manage our product strategy and roadmaps so we need to have integration between the 2 systems in order to maintain continuity o...

What is the challenge? Enable OKRs in your workspace and your workspace line, and create some OKRs as multiple levels Make sure you have the out of the box Key Results field on your feature/epic screen Click on the Key Results field. What is...

What is the challenge? Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this...

What is the challenge? We have several documentation sets in Aha! Knowledge serving different user groups and languages, but right now we can only configure a single base URL for each knowledge base. We need to publish different content (sometim...

I work in a group that has many workspaces. We would like to be able to define automations at the Product Line level that will impact all workspaces underneath it or at least be available to the workspaces underneath it.