Despite your careful research, consideration, and planning - that epic you fought for inclusion into a release just isn't going to get started any time soon. Sprints later you realize that it's probably not going to happen ever. Holding on to hope...
Erik Didriksen
about 6 years ago
in Epics
0
Already exists
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
about 6 years ago
in Epics
1
Unlikely to implement
Add the ability to customize Master Feature cards on the Master Features Road Map
The Master Features Road Map does a great job of showing what master features we are working on in each release and the why. The why being the goals and initiatives they support. Those releases are organized by external due dates and show nicely. ...
Guest
over 6 years ago
in Epics
0
Unlikely to implement
The History for linking and unlinking features to master features.
We need a way of identifying any scope creep by viewing the history of a master feature to see if any new features have been linked to it.
This functionality is available at a feature level as you can see all requirements that are linked to it.
Guest
almost 7 years ago
in Epics
0
Already exists
Under Reports / Roadmap / Features
in customize view we select "show master features" as we want to show both master features and features
we can add filter on feature tags : this works fine
but if we add filter on master tags for e.g. : it isn't...
Agnes Muller
almost 7 years ago
in Epics
0
Unlikely to implement
Add "For workspace" field for epic layout that reflects the release's workspace
What is the challenge? Users need to click into a release to see which workspace an epic's sits in. This is not very intuitive for new users and adds an unnecessary extra click to view a critical piece of information. Release has many definitions ...
Max Klin
3 months ago
in Epics
1
Future consideration
Allow epics to inherit prioritisation scores from features
What is the challenge? We prioritise features, not epics. However, it's still useful for many reasons (e.g. reporting) to have a prioritised view of epics as well. There's no way that we will spend the time to score epics separately though. What i...
John P
6 months ago
in Epics
0
Future consideration
When cloning, please provide ability to clear values in custom fields before saving in Domain Epics/Epics
What is the challenge? User clone records, without cleaning the existing data that is not applicable for the new record. What is the impact? Data consistency and re-work Describe your idea Have an option, when cloning to reset all the other attrib...
Edgar Holguin
10 months ago
in Epics
0
Future consideration
What is the challenge? User have dependencies at Features, but if they Epic reports they will need to set up a new dependency to show in reports. What is the impact? Manual creation at the parent level, might be missed by the user. Describe your i...
Edgar Holguin
about 1 year ago
in Epics
0
Future consideration
Weigh epics based on story points for initiative progress
Not all of my epics under an initiative are equal size and Aha is considering them that way, which makes the progress inaccurate. For example, there are 5 epics under an initiative and Aha is treating them all as 20% of the Initiative. I want to t...