If you are required to spend no more than 5 working days for the epic and you are not sure about one extra task to be included in the scope – check the epic remaining time. You can be sure: not a tiniest sub-task logged time passed uncounted.
Just include the relevant issues in the Epic and get their logged work time aggregated to the Epic Time Spent field. The Epic Remaining field will automatically show how much time left for the Epic.
Should you hurry up or you have enough time for your task? See how much time the epic allows you to spend (there are no restrictions, it's just nice to know). Each work log entry will update this information for all your coworkers making time control much easier.
Ensure that your issue has a parent Epic issue and get the Epic Estimate and other EpicTime fields information auto-populated.
Find easily the epics with estimated time overrun: generate the EpicTime report and sort the issues by the Ratio or the Remaining column. Go to an issue right from the report to see the details and handle the problem.
EpicTime for Jira Cloud provides a user the web-section with following fields:
- Epic Estimate
- Epic Time Spent
- Epic Remaining
- Epic Ratio
- Epic Key
These fields to be displayed in any issue type but act a bit variously herewith:
- In an issue of the Epic type, the app aggregates time logged in the Epic itself and in all its child issues to the Epic Time Spent field and auto-populate the Epic Remaining and Epic Ratio (percentage of spent time to the estimated time) fields in accordance.
- In an issue of another type, the fields display information from the parent Epic.
Just include your issue to an Epic to get the information from this Epic and also to make the issue's logged time included to the Epic's spent time.