What is the challenge? We want to distinguish between Epics which end up in the product, and Enablers which are required to deliver the product but not a part of the product itself What is the impact? By not having a record type of Enabler, we can...
Guest
3 months ago
in Epic
0
Unlikely to implement
Configure so that epics and feature dates are following release dates
I would like to be able to configure so that the master features (MF) and features (F) follows the release date. This would be very helpful during sprint planning and replanning. The bulk editing is a work around, but still when you move around th...
Kristian Haglund
over 5 years ago
in Epic
1
Unlikely to implement
Allow roll-up of feature scores to linked master feature
It would be helpful to allow a roll-up total of feature scores to a linked master feature. This is a requirement we have right now as we prepare to launch our custom scorecards on features.
Use Case:- I have multiple features with scores that are ...
Guest
over 6 years ago
in Epic
1
Unlikely to implement
We've started building out our roadmap in Aha! using the Epics functionality. One thing I have found tricky is locating Epics after I've created them, as I can only see them within the context of a Release or Parking Lot. After enabling the "List"...
Guest
over 4 years ago
in Epic
2
Unlikely to implement
We use master features to define use cases that require work from multiple products. The features linked to the master feature come from those different products. However, we need the ability to put requirements on a master feature to be able to t...
Guest
over 6 years ago
in Epic
0
Unlikely to implement
There are times when a Master Feature gets released into multiple Releases. It would be nice to see the master feature and all the releases associated with it form the Gantt Chart.
Guest
almost 5 years ago
in Epic
2
Unlikely to implement
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