Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Epic

Showing 143 of 8276

Additional time fields for customizing record cards

I would like to be able to have the option to add the original estimate, remaining estimate, and logged time fields to my feature and master feature cards (just like how I can pull them into a pivot table). It is helpful to see the original estima...
Guest over 4 years ago in Epic 1 Future consideration

Sharing Master Features between Products

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...
Guest almost 5 years ago in Epic 0 Already exists

Add Master features toggle to List view

Working with both features and master features we find the toggle to view either Master features or features in the Board view really useful. However, we really miss the same toggle in the List view where we only can see features. Please include t...
Andreas Moritz over 2 years ago in Epic 0 Future consideration

Linking features to more than one master feature

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 b...
Guest about 5 years ago in Epic 0 Will not implement

The History for linking and unlinking features to master features.

We need a way of identifying any scope creep by viewing the history of a master feature to see if any new features have been linked to it. This functionality is available at a feature level as you can see all requirements that are linked to it.
Guest about 5 years ago in Epic 0 Future consideration

Visually represent the size of a feature with larger or smaller cards

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...
Nate Dunlevy about 5 years ago in Epic 1 Unlikely to implement

Restrict access to bulk actions

We have 20+ people in Contributor role working on the same Product. All of them have by design access to bulk actions and can inadvertably bulk delete all of the hundreds of items that we have in Aha!. We want to somehow restrict access to bulk ac...
Guest over 5 years ago in Epic 0 Unlikely to implement

Custom fields on Record Cards

I've created custom fields for epics and I'd like to be able to add them to the Epic Record Cards. There seem to be only default fields available when I edit the Record Cards layouts.
Sharon D over 2 years ago in Epic 3 Already exists

Need specific support for user journeys

The customer success team suggested I just use initiatives for user journeys and master features for user journey steps, which is a good temporary fix. However, defining a user journey is a pretty specific thing that I think should be set apart fr...
Mike Mitchell over 5 years ago in Epic 2 Unlikely to implement

Display master features for current product first

When applying a Master feature to a feature, you have to scroll through all the products' master features if your product is at the bottom of the list. It would be great if the Master Features for the Product you are currently navigating were at t...
Guest almost 6 years ago in Epic 0 Future consideration