Skip to Main Content
ADD A NEW IDEA

Epic

Showing 148

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

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 almost 6 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 almost 6 years ago in Epic 0 Unlikely to implement

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 6 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 over 6 years ago in Epic 0 Future consideration

Asking for more user-friendly IDs for custom table entries

What is the challenge? The current Custom table record IDs (e.g. 7576123412341234123) are long, complex, and difficult for users to remember and manage. What is the impact? Difficulty in communication and collaboration when users need to share or ...
Tanya Lin about 1 month ago in Epic 0 Future consideration

Automatically populate Epic end/due date only when last feature is completed, instead of continuously

What is the challenge? Epic due date is updated continuously when underlying features are completed/done if due date is set to "Calculate from features". What is the impact? Gives a "false positive" indication of an epic's due date which in turn i...
Mats Hultgren about 2 months ago in Epic 0 Future consideration

Progress Bar- show color-coding from the Epic % complete

Who would benefit? Teams that work in Jira or teams that want to more easily see how Features are progressing What impact would it make? It gives more insight than just a Feature being done and the Epic progressing How should it work? Similar to h...
Jonathan bohaty 7 months ago in Epic 0 Future consideration

make it easier to work with Epics

Who would benefit? PMs What impact would it make? Ability to more quickly prioritize, sequence and schedule work in the context of user need driven planning (epics) as opposed to functionality driven planning (features) How should it work? If you ...
Guest 7 months ago in Epic 0 Future consideration