How to manage progress calculation settings for Jira epics & issues as KRs? (Before v3.8.8)
Annu
Jira epics and issues when attached to objectives, can be configured to consider sub-tasks for progress calculation. Here's how you can manage that.
Progress calculation when Epics are key results
Employee Success allows you to add Jira epics as key results. However, Jira epics are the special type of issues which act as a container for other Jira issues. In turn, those Jira issues can have their own sub-tasks.
In such a scenario, the KR progress calculation can be based on the highlighted 3 options. Therefore the system allows you to manage these configurations to get desired progress calculations. Refer the image below to see what options are available.
All 3 checkboxes are true
By default, all of three options are checked. If the first option is true then remaining two are also true by default and you cannot make a change in that.
When all three checkboxes are true, the system calculates the epic key result progress on the basis of subtasks within the Jira issues contained in the epic. Every Jira epic may or may not have Jira issues and subtasks within Jira issues, however, the bottom line is the progress of epic key result will be calculated on the basis of subtask's resolution. If there are no subtasks then the number of Jira issues & their resolution is considered.
Last 2 checkboxes are true
When last two checkboxes are true, the system calculates the epic key result progress on the basis of Jira issues contained in the epic. Depending on the number of issues in the epic, progress contribution of each issue is decided and displayed as the progress of epic key result according to their resolution. If there are no Jira issues in the epic, the system considers the resolution of the epic and the progress will be shown 0% or 100% on the basis of resolution is empty or not empty.
When only last two checkboxes are true, even if there are any subtasks in Jira issues, the system completely ignores that and shows the progress on the basis of the number and resolution of the Jira issue.
Only last one checkbox is true
When only last one checkbox is true (this becomes mandatory if first two are false), the system calculates the epic key result progress on the basis of the resolution of the epic itself. Which means, if the resolution is empty, the progress of epic key result would be 0%. If the resolution is not empty, the progress of epic key result would be 100%.
When only last one checkbox is true, even if there are any Jira issues or within the epic, the system completely ignores them and shows the progress on the basis of the resolution of the epic.
Progress calculation when Issues other than Epics are key results
Like Jira epics, you can also add your Jira issues as key results. Jira issues work as containers for subtask and it might be important to consider the progress of subtasks within Jira issue to measure the progress of Jira issue key results.
As shown in the image below, the system provides you two options whether you want to consider subtasks or Jira issue resolution to measure Jira issue key result progress.
Both check boxes are true
When both the options
Last checkbox is true
When the last option - r
Read How does the progress calculation of Jira issues and epics works? to know details of this feature.
Whenever any changes are made in these settings, existing Jira epics and issue key results will get recalculated according to the changes in these settings.
On this page
In this section
- Concepts - OKRs & objective cycles
- How do I add UpRaise attributes to Jira issues as custom fields?
- How to view UpRaise OKRs on Jira board?
- How do I create, edit & delete an objective cycle?
- How do I modify grading settings for company, team or individual OKRs?
- Jira issues/epics as KRs or Jira issues/epics as actions?
- Reopen an objective
- What are the attributes of an objective cycle?
- What are the different statuses of an objective cycle?
- Manage tab (previously OKR advanced settings) on OKR page
- Company OKR settings