Features

What is the challenge? If you are using a feature as a template for repeatable work and it includes a series of child requirements, copying the feature does copy the child requirements but any record relationship links between the copied require...

Would like to see an option in the account / workspace to only allow features to be associated with the same release as the epic.

When you create or copy a feature, its ID is automatically created based on the product code. The ID is a combination of the product code and an auto number (and that is perfectly fine). But when you change the release reference to a release of an...

What is the challenge? PMs need to manually break bigger pieces of work (initiatives, epics and features) down into smaller pieces of work What is the impact? PMs spend their time on this activity, instead of focusing on more strategic wor...

What is the challenge? Product related information may reside in multiple tools/artefacts. This needs to be summarized on the appropriate Aha! record What is the impact? Significantly reduce the amount of time taken to summarize requiremen...

What is the challenge? When working on the epics/feature board, I need to see the release progress for each without needing to click on the release name to see the progress. We have multiple releases that are in progress at any given time and this...

As a large enterprise we use O365, OneDrive, Planner, Project Online, Groups, Etc. Native Integrations would be nice.

This would allow for an easy view that can be used to review and prioritize features, especially when features across multiple products have dependencies. Viewing and filtering multiple releases from different products in the same features board w...

It would be extremely useful to be able to look at a report and understand the "last updated" date so you would know if there is updated content. The "last updated" date would change if any of the content in the report underwent a revision/change.

What is the challenge? We often know we will have work in future releases which are reliant on other teams to define or which we want to plan to leave space to work on but we don't yet have all the information. We currently write [Placeholder] in ...