Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Epic

Showing 20

Change Master Feature Prefix

The Prefix for all Master Features is 'E', this is a suggestion to change this globally to M to align with the default terminology. EG PRODUCT-E-123 should be PRODUCT-M-123 instead.
Guest over 5 years ago in Epic 1 Unlikely to 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 over 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 over 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 almost 7 years ago in Epic 2 Unlikely to implement

Renaming Master Features "Epics" will confuse those of us with Jira integrations.

Just wanted to make you aware that renaming Master Features "Epics" will be confusing to those of us with Jira integrations. We integrate Features with Epics in Jira.
Avigail Ehrenhaus over 4 years ago in Epic 0 Unlikely to implement

Initiative progress field calculation by completed master features

A common agile practice is to track progress by the burn up of completed things. I see there is already this kind of calculation for completed features. Need the same thinking to be applied to tracking initiative progress by calculating subordinat...
Richard M over 4 years ago in Epic 0 Unlikely to implement

Contractual Committments

For B2B enterprise products, it would be good to be able to track customer committed deliverables. Right now we have to do a few work arounds: follow a naming convention for ideas or tags for features to associate "client contract scope items". Th...
Guest over 4 years ago in Epic 0 Unlikely to implement

Show Roll Up Initiatives in MasterFeature/Feature Card

I would like to be able to show roll up initiatives on the Master Feature and Feature cards. We use the hierarchy: * Initiative Roll Up = Initiative/Project/Program (depending on situation) ** Initiative = Project Epics *** Master Features = Epic...
Kristian Haglund over 5 years ago in Epic 0 Unlikely to implement

Choose which non-shipped features move with a Master Feature

Currently if you move a Master Feature to another release it will ask you if you want to move all of the non-shipped features. This enhancement request is asking to be able to checkbox select which features you want to move. See example, I would w...
Guest over 5 years ago in Epic 0 Unlikely to implement

Bulk Edit "Ideas" promoting to new "Features" and linked to a single "Master Feature"

Currently, it is possible bulk edit a set of ideas and move them to individual "features" on the feature board. However, there is a use case to at the same time, link these features to a single "master feature." I cannot find a way to do this in a...
Guest over 6 years ago in Epic 0 Unlikely to implement