How to bifurcate Time spent and Time remaining in Time-Tracking field for Standard and Subtask issue type
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Purpose
The sum of Time spent and Time remaining in the Time-Tracking field is inconsistent as the same field is used by the Parent and Sub-Task.
Environment
Jira Cloud
Solution
Here we will be discussing the Original estimate and Time tracking field on Standard and sub-task issue type.
When a sub-task is associated to a standard issue type (Story/Task) the Time tracked on parent issue will show value from sub-task when Include subtasks is checked.
When we add Original estimate on parent issue, the Time tracking will show time as sum of Subtask as well as Parent issue. Field "Time tracking - Time remaining" is a summation of remaining on the parent + remaining on the Sub-tasks combined. You can refer issue history to view changes made to Remaining Estimate and Original Estimate.
Before adding/changing Time remaining on parent issue
After adding/changing Time remaining on parent issue
If you wish to track the time of the Parent issue without affecting the efforts from the subtask then you need to create a custom time tracking field and map it to the Parent issue type and educate users to log work/track time for the standard/parent issue type using the custom field. Article How to create time reports based on Custom fields? can be used if you wish to generate reports for work done specifically on standard issue type.