This article is for Data Center. Visit Cloud
Progress Based on Time Tracking
- Jaramy Conners
When Issue Progress is based on Time Tracking within a Progress column, the progress is calculated based on the issue's Resolution field, time tracking data, and the progress of its sub-issues.
Calculating Progress for Issue Without Sub-Issues
If the issue does not have sub-issues:
- If the issue's Resolution field is not empty, and Apply Resolution is turned on, the progress is 100%.
- Otherwise, if the issue has time tracking information, the progress is calculated proportionally to this issue completion %:Â
(Time Spent) / (Time Spent + Remaining Estimate) - Otherwise, the progress is 0%.
Calculating Progress for Issue with Sub-Issues
If the issue has sub-issues:
- If the issue's Resolution field is not empty, and Apply Resolution is turned on, the progress is 100% - regardless of the sub-issues' progress.
- If the issue and its sub-issues do not have estimates or work logged (or if time tracking is turned off), the progress is calculated as the average of the sub-issues' progresses.
- If time tracking is used and all issues have an estimate (either original estimate or remaining estimate), the estimates and total work logged are summed up and the progress is calculated as the total completion %:Â
(Total Time Spent) / (Total Time Spent + Total Remaining Estimate)- If a sub-issue does not have time tracking information, it is counted in as an average sub-issue, based on the mean total time (time spent + remaining estimate) of its siblings.
If the issue has both its own time tracking information and sub-issues with progress, and if Ignore Parent Issue Progress is turned off, the issue's own progress value is counted as if it was the progress of another sub-issue.
Examples
1. Without Time Estimates
Â
Issue | Explanation | Progress |
|---|---|---|
Sub-sub-issue 2.1 | The issue is resolved (indicated by the green mark), so it is complete. | 100% |
Sub-issue 2 | It has two sub-issues with 100% and 0% progress; the total progress is the average of the two. | 50% |
Top issue | It has two Sub-issues: sub-issue 1 is 0% done and Sub-issue 2 is 50% done; the mean value is 25%. | 25% |
2. With Time Tracking Information
Issue | Explanation | Progress |
|---|---|---|
Sub-issue 1 | It has 3 days of work logged with 1 day remaining, so its progress is | 75% |
Sub-issue 2 | This issue does not have any work logged, is not resolved and does not have sub-issues. | 0% |
Top issue      | The top issue has a total time spent of 3 days (work logged on Sub-issue 1) and 2 total days remaining (estimates on Sub-issue 1 and Sub-issue 2), so its progress | 60% |
3. More Complex Example
Issue | Explanation | Progress |
|---|---|---|
Sub-sub-issue 2.1 | It has 2 days of work logged with 1 day remaining, so its progress is | 66% |
Sub-sub-issue 2.2 | This issue has 1 day of work logged and no work remaining - so even though it is not resolved, it's considered completed. | 100% |
Sub-issue 2 | It has total time spent of 3 days, and total remaining estimate of 2 days (the remaining time from Sub-sub-issue 2.1 and its own 1 day, which is considered additional work). The progress is | 60% |
Sub-issue 1 | This one has 3 days of work logged and 1 day remaining, so its progress is | 75% |
Top issue                 | The obvious total time spent is 6 days with a total remaining estimate of 3 days (the count from all sub-issues on all levels). But there's also Sub-issue 3, which does not have any estimates or work logged, so it gets estimated based on the average of its siblings - Sub-issue 1 and Sub-issue 2. The progress of the top issue is calculated as follows:
| 44% |