Epic
Sort by:
Popular
Status:
Showing 147
2
VOTE
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...
0
Will not implement
2
VOTE
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...
1
Unlikely to implement
2
VOTE
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...
0
Unlikely to implement
2
VOTE
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...
2
Unlikely to implement
2
VOTE
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...
0
Future consideration
1
VOTE
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 ...
0
Future consideration
1
VOTE
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...
0
Future consideration
1
VOTE
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...
0
Future consideration
1
VOTE
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 ...
0
Future consideration
1
VOTE
Bug: If your epic layout has Status but not Team you don't see the status. You can only see the status if you have Team enabled too, since it's like a sub-component on the Team layout row
Who would benefit? Anyone trying to optimize their layouts What impact would it make? You wouldn't waste time trying to figure out why the status row wasn't showing up How should it work? It would either show you the status row even if you didn't ...
1
Already exists