Jira issues/Epics as KRs or Jira issues/epics as Actions
- Annu
Background
There are two schools of thought with regards to whether Jira issues make for good key results or not. While we think there is no harm in making Jira issues/Epics as Key results of UpRaise Objectives (this has to be done mindfully though, not every Jira issue can qualify as a Key result), there are a handful of customers who think Jira issues/Epics should not be Key results. They think its better to connect them with Key results as Actions (sometimes called as Initiatives).
UpRaise now supports both approaches. In fact, one can configure both to be possible at the same time, but we don't recommend that.
Jira issues as KRs
If you look at image below, there are only two layers in the OKR hierarchy, i.e. Objective and Key Results.
So in this approach, Jira issues or Epics can be added as Key results. They, in turn, will have an impact on objective progress. UpRaise allows you to configure Jira issues and Epics in a way so the progress calculations can be done in various ways depending on issues contained in the Epic & Sub-tasks contained in issues.
Jira issues as Actions for KRs
This way one can add Jira issues or Epics as Actions within Metric and To do type KRs. These actions will not have any impact on the progress of Metric or To do. However, their purpose is to provide a connection between day to day tasks (i.e. Jira issues) & the expected end result (i.e. Key result).
Example - You have a metric KR that says 'Reduce page loading time by 5 seconds'. To reduce the page loading time you will have some issue within your Jira, that particular Jira issue can be added as an Action within the Metric KR.
This is a typical example of Metric and Jira issue, however, the Metric can be anything related to your technical and non-technical projects and it allows you to add Jira issues and Epics as Actions from different projects at a time. Take a look at the image below to understand the hierarchy.
