Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Epics

Showing 178

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 6 years ago in Epics 1 Already exists

Add more granularity to the progress bar

It would be really great if the progress bar could be colour coded so that for each feature against an epic its status could be represented in its individual colour becoming progressively dark green as it more features are completed
Mark Colonnese over 3 years ago in Epics 0 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 over 6 years ago in Epics 0 Already exists

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 boar...
Guest almost 7 years ago in Epics 0 Will not implement

Allow @mention in Aha comment

When commenting in Aha text area, we need the @user mention functionality.
Guest over 3 years ago in Epics 4 Already exists

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 7 years ago in Epics 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 about 7 years ago in Epics 0 Unlikely to implement

Make Notes, available as a relationship custom field

We use notes to capture information related to the EPIC. While there are other custom fields that can be added natively to an EPICS's layout Notes is not one. The only way I've seen to attach a NOTE to an EPIC is making it RELATED. The issue with ...
Eugene Peters over 3 years ago in Epics / Notes 0 Future consideration

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 7 years ago in Epics 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 over 7 years ago in Epics 0 Already exists