We are trying to use SCRUM boards to manage progress on a sprint based project.
We have a number of epics. Each epic is decomposed into a set of user stories, and each story is decomposed into a number of sub tasks.
The first problem is that time logging at a sub task level isn't registered as progress at the user story level. I've seen a few postings here that say that this is how the product is designed to work, but its plainly counter intuitive to not support roll up of sub task estimates and progress.
Elsewhere I've seen suggestions that the way to address this is to remove the estimates from the story level, but in doing so this undermines aggregate estimates at the epic level. Hence, if I remove user story level estimates there are no estimates available at an epic level - again this is plainly counter intuitive.
My inference is that you already have the correct aggregation logic for estimates and remaining time delivered for how 'epic' stories work. Why can't the same logic be introducted for user stories and sub tasks??
My suggestion would be to:
* Add a project level configuration option that allows parent issue time estimates and remaining time values to be drawn from subordinate issues where such child issue data exists
* Alternatively add some extra fields at an issue level for storing the aggregate child issue time estimates and remaining time values.
