Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Excerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
How Jira epics and issue key result progress calculation works?https://amoeboids.atlassian.net/wiki/spaces/UPFJ/pages/1377370151/How+to+manage+progress+calculation+settings+for+Jira+epics+issues+as+KRs are available to determine the way to calculate the progress of Jira’s epic & issues other than epic with two options given below.
Progress calculation when Jira epic is key result
When a Jira epic is added as KR to an objective, that epic may or may not contain issues & subtasks. While calculating the progress of such epic KRs, system checks whether at the bottom stage there is a subtask or an issue, depending on the hierarchy of the epic, system starts checking the resolution staus category of that bottom stage. Calculation on the basis of status category
ExampleIf an epic contains 2 Jira issues & each of those 2 issues contain 5 subtasks, each of them automatically contributes 20% of progress to the Jira issue when the status category of the issue is
As per this example, the progress is derived from a subtask to Jira issue and then to an epic. Consider the example shown in the image below.
If there are no subtasks in the Jira issue of an epic, the system considers the status category of the Jira issue to calculate the progress (applicable in both configurations). Calculation on the basis of custom fieldWhen the settings are configured to calculate the progress on custom fields, system looks for the last level of the issue and its custom field value to calculate the progress of the epic. Example - Assume, an epic contains 2 Jira issues. Jira issue 1 has 3 subtasks in it & Jira issue 2 has 2 subtasks. The calculation of the progress is done on the basis of custom field which is why calculation will be done considering the value of custom field as well as the custom field of the weightage. If the custom weightage custom field is not defined, system will take the equal & default weightage for progress calculation. As per this example, the progress is derived from a subtask to Jira issue and then to an epic. Consider the example shown in the image below.
(Subtask 1's custom field value * its weightage custom field value) + (Subtask 2's custom field value * its weightage custom field value) + (Subtask 3's custom field value * its weightage custom field value) / addition of all weightage values. = (30*10) + (40*5) + (50*5) / 10+5+5 = 300+200+250/20 = 37.5 Hence, Jira issue 1 progress % = 37.5
(Subtask 1's progress * its weightage custom field value) + (Subtask 2's progress * its default weightage) / addition of all weightages. = (100*5) + (100*5) / 5+5 = 500 + 500 / 10 = 1000/ 10 = 100 Hence, the progress % of Jira issue 2 is 100.
(Jira issue 1's progress % * its weightage custom field value ) + (Jira issue 2's progress % * its weightage custom field value ) = (37.5*7) + (100*5) / 7+7 = 262.5 + 700 / 14 = 962.5/14 = 68.75 Hence, the progress of epic Kr 68.75% Progress calculation when issues other than epic are key results
|
Status | ||||
---|---|---|---|---|
|
Jira issue 2 has no subtask as well as it's Sttatus category is
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||
---|---|---|
|
Calculation on the basis of custom fields
When issues other than epic are added as KRs, the progress of issue KR can be calculated on the basis of task contained in it. When calculating this progress on the basis of the custom field, the workflow would be something like shown in the image below. Let us see an example of this progress calculation.
Example - Jira issue 1 contains 3 subtasks & Jira issue two contains 2 subtasks. Subtasks in Jira issue one have some custom fields applicable o them. In Jira issue 2, it's subtask does not match with the defined custom field.
Progress calculation of Jira issue 1 -
(Subtask 1's custom field value * its weightage custom field value) + (Subtask 2's custom field value * its weightage custom field value) + (Subtask 3's custom field value * its weightage custom field value) / addition of all weightage values
=(20*5) + (25*2) + (5*5)/ 5+2+5
=100+50+25/12
= 175/12 = 14.58
Hence, the progress of Jira issue 1 is 14.58 %
Progress calculation of Jira issue 2 -
In Jira issue 2, the custom fields are not applicable, therefore system considers their resolution status category fields. Also for subtask 2 in Jira issue 2, the weightage field is not applicable. Therefore, the default weightage of 4 is considered here.
(Subtask 1's custom field value * its weightage custom field value) + (Subtask 2's custom field value * its weightage custom field value) / addition of all weightage values
= (100*5) + (100*5) / 5+5
= 500+500/10
= 1000/10 = 100
Hence, the progress of Jira issue 1 is 100 %
On this page
Table of Contents |
---|
Iframe | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|