Time tracking from Issues not rolling up to Epic

[Stephanie Heacox]

The new ticket layout seems to indicate that time logged to Issues which are part of Epics should show up (and roll up) under the Epic ticket:

However, as you can see, the "Issues in this epic" section says the issues are "0% done", which is absolutely incorrect - most of those tickets are near complete.  There seems to be a disconnect here, and I have been unable to resolve it.  Can someone assist? 

[Sachin]

Hello @Stephanie Heacox , you need to move your issues into "Done" status for the epic progress bar to consider that work is being done on the child issues under that epic.



Note: Jira considers an issue as closed when the "Resolution" field has a value.

[Stephanie Heacox]

Okay, then this function is much less useful than it could be.  I need to know what percentage of the combined tickets has been completed SO FAR, not just the binary of DONE.  In other words, how many hours (or what percent) of this epic is left?  This information is needed to track progress, long before the individual issues are finished.  At the very least, it would be helpful in this view to see the progress bars for each of the issues, instead of IN PROGRESS.

[Blake Duerden]

I agree. We have had designers logging time to tasks and subtasks within an Epic that has an Original Estimate but that time is not recognised.

So the overall 'project' (Epic) is not recognising it's constituent parts. The sum of the parts is definitely not equalling the whole. Mind-bogglingly redundant feature to include time tracking that doesn't in fact track

[Madhu_RVS]

Hi @Blake Duerden , @Stephanie Heacox 

If you would be interested in a mktplace app to get this data, you can try out

Issue Hierarchy Reports 

And generate insights such as:

- % complete based on time spent and story points at each hierarchy level

- Sum up Time Spent, Org Estimate, Time Rmng, custom number
fields