You are viewing documentation for Structure Server and Data Center version 5.5 and patch releases. For other versions, see Version Index or [Structure Cloud].
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.
If the issue does not have sub-issues:
(Time Spent) / (Time Spent + Remaining Estimate)
If the issue has sub-issues:
(Total Time Spent) / (Total Time Spent + Total Remaining Estimate)
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.
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% |
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% |
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% |