What is the challenge? Epic templates (i.e. for the description) are currently managed under 'workflows'. Why is this under 'workflow', and not under 'Epic layout'? That doesn't make much sense. Currently, there is no way to create a template for ...

Use case: there are times when I need to prioritize my list based on a custom scorecard that we've added as a custom field. It becomes hard to do this because I can't hide, remove or re-arrange the order of the product value score column.

What is the challenge? There is a "Feature columns delivery risks" field available in reporting for features that summarizes all the delivery risks for that feature. Though you can flag initiative records with risks as well, that summary field is ...

What is the challenge? The Remaining effort field is not currently supported in calculation columns. Also it's not possible to sort or filter on this column. What is the impact? It's difficult to get value from the Remaining effort field i...

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? Currently, Aha! does not support expandable macros (e.g., collapsible sections) coming from Jira Description. What is the impact? This leads to significant data loss — important contextual information, formatting, or...

What is the challenge? AI summaries exist on the frontend for customer use, but there’s no equivalent for writers working in the backend. What is the impact? Writers can’t easily query existing content, identify where updates are needed, or scale ...

What is the challenge? When OKRs are enabled, there are 3 fields to track: Target metric Starting metric Current metric However, there is no ability to track changes to these values over time. The need is highest for the "Current metric" field. Wh...

By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...

It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.