Reading the actual problems about using epics and being restricted to a 2-level-hierarchy we re going to use epics only as a collections of stories and tasks very similar to another kind of meta tags (-> labels). Now we should be able to identify the high level tasks on the "big picture" of our to be developed application. This about 20 epics will be related to about 100 stories which are the highest hierarchy level in GH sprints.
As we re now going to evaluate effort on the epic level i would like to notice them in each epic issue, but for my understanding there will be no summarize function like JIRA provides on a story/task <-> subtask, isn t it? So i would have to update the spent effort time by time manually? In fact because of the missing link nobody really will work on them, so it s only a workaround but no solution!
Additionaly i put all these epics to an individual version (without any parent) in order not to mix up any efforts, is this a possible option?
In a perfect world there would be following structure:
Epics <-> Stories <-> Tasks <-> Sub-Tasks 1.level <-> Sub-Tasks 2.level <-> Sub-Tasks n.level
All efforts are summarized to the (single) parent issue, all other relations via issue linking is just informational. If no estimated effort is entered on the parent just calculate them from the childs, otherwise take the manual entered one, effort spent should be summed up. This would ease up the initial effort estimation (can be done on epics -> top-down) and will be improved while working on the stuff itself (bottom-up).
At the moment i cannot understand why this should be as complexe, so please hurry up to enable all JIRA customers to work like this, thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.