It seems like an Epic should be created as a task, then we would use sub-tasks (maybe sub-sub-tasks) to map out development tasks.
But trying to do this we run into problems...
- A sub-task can be in additional folders to its parent, but it HAS to be in the same folders as its parent. So If I put Epic1 in a sprint but some sub-tasks will spill into a future sprint, it screws up gantt and other views.
- Maybe we should keep Epic1 outside the sprint and only put sub-tasks in individual sprints. But then where should the parent live?
- Subtasks don't really show that they are sub-tasks well so we have to give them very verbose names like Epic1: Do the thing
- I can't see a task automatically can set it's start/end dates based on its sub-tasks, or let us see % completion, total time spent, etc
I've seen quite a few posts about sub-tasks in different areas. I'd initially thought they were full tasks in their own right, now I'm not sure if they are limited or not.
Iniciar sesión para dejar un comentario.