Epics

We want to use the Custom Roadmap Report, but one gap we've found is that in the customize view you can color by Feature Status but not Master Feature Status. This would help us to provide higher level roadmap updates.

When editing the titles of master features (or I assume it applies to any item like features, initiatives, releases, etc), the text editor should display multiple lines instead of just one. For long titles, the one-line display results in having t...

Different roles need different details to be visible at a glance. Managers need more details than viewers. Allowing different default customized layouts per role would be helpful to keep cards as clean and focused as possible for viewers while bei...

as a product owner, i need to know what card is highest priority in the under consideration column (at least) in order to pick the most important card up for analysis unlike right now, there is a random order applied that does not correlate to any...

We deliver customer solutions on top of our base product which often drive the development of (future) features in our base product. Because we have to manage these features separately as part of delivery of this customer "product", we then find w...

We would like to be able to convert a text-based field to a note-based field in custom layouts by editing the field. Use case: We set up a set of fields to build a report, and one field (path to green) is a text field. We've since realised that th...

I have a solution A which is made up of features X and Y from products B and C respectively. However, X and Y may also be features in solution B. With the recent update, you’re able to view master features along with features on the feature boar...

I would like to create a custom drop down field that appears on all Epics that use a shared layout. The custom field should be the available values in another custom field for a specific workspace. To illustrate: * On workspaces 1-10, I want to ad...

Aha! Develop allows teams to have a unique layout for features and requirements. This helps them see the information they need for development, while hiding the information they don't. Please support this for epics as well.

In Aha, it's difficult to represent the relative effort required for different master features and features. Time is not the only consideration. For example, so features have dependencies that while not requiring heavy effort, will effect the dura...