This article is for Cloud. Visit Data Center
Progress Based on Percent Field
- Jaramy Conners
When Issue Progress is based on a custom percent field, the progress is assigned to each issue manually in a custom field, and progress is aggregated for parent issues.
You can use any numeric Jira custom field to store the current progress % – a value from 0 to 100.
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%.
- If the issue's Custom Field value is not empty and is between 0 and 100, it's considered as the completion progress in percents.
- If the issue's Custom Field value is less than 0, the progress is 0%; if greater than 100, the progress is 100%.
- Otherwise, the progress is undefined. The issue neither shows any progress, nor affects the progress of its parent issue.
Calculating Progress for Issue with Sub-Issues
If the issue does have 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's Custom Field value is not empty, it's considered as that issue's completion progress in percents (from 0 to 100) – regardless of the sub-issues' progress.
- Otherwise, the issue's progress is the weighted average of its sub-issues.
You can specify how an issue's weight is determined in the column configuration panel.
Examples
1. Percent Field, All Sub-Issues Are Equal
With a Custom field named Complete, total progress based on All Sub-Issues Are Equal, and Apply Resolution turned on.
Issue | Explanation | Progress |
|---|---|---|
Sub-sub-issue 1.1 | This issue is 50% complete as specified by the custom field. | 50% |
Sub-sub-issue 1.2 | This issue is resolved (indicated by the green mark) - so it is complete, even if the "Complete" field is empty. | 100% |
Sub-sub-issue 1.3 | This issue has no progress information (neither "Resolution" nor "Complete" fields), so progress is undefined and not counted at all. | n/a |
Sub-sub-issue 1.4 | This issue has a 0 "Complete" value, which means it's 0% complete. | 0% |
Sub-issue 1 | It has four sub-issues, but 1.3 is ignored. So the total progress is the average of the rest: (50 + 100 + 0) / 3. | 50% |
Sub-issue 2 | The issue is 25% complete as specified by the custom field. | 25% |
Top issue | It has two sub-issues: Sub-issue 1 is 50% done and Sub-issue 2 is 25% done. So the progress is the average of the two: (25 + 50) / 2. | 38% |
2. Percent Field, Story Points
With a Custom field named Complete, total progress based on the field Story Points, and Apply Resolution turned on.
Issue | Explanation | Progress |
|---|---|---|
Sub-sub-issue 1.1 | This issue is 50% complete as specified by the custom field. | 50% |
Sub-sub-issue 1.2 | This issue is resolved (indicated by the green mark) - so it is complete, even if the "Complete" field is empty. | 100% |
Sub-sub-issue 1.3 | This issue has no progress information (neither "Resolution" nor "Complete" fields), so progress is undefined and not counted at all. | n/a |
Sub-sub-issue 1.4 | This issue has a 0 "Complete" value, which means it's 0% complete. | 0% |
Sub-issue 1 | It has four sub-issues, and weight is based on story points:
The total progress is the weighted average of 1.1, 1.2 and 1.4: (50 x 2 + 100 x 3 + 0 x 2.5) / (2 + 3 + 2.5). | 53% |
Sub-issue 2 | The issue is 25% complete as specified by the custom field. | 25% |
Top issue | It has two sub-issues: Sub-issue 1 is 53% done and has 7.5 story points; Sub-issue 2 is 25% done and has 1 story point. So the progress is calculated as (53 x 7.5 + 25 x 1) / (7.5 + 1). | 50% |