Metric and To doNavigate to relevant objective where you want to create a Key result. Click on Add new in under Key Results section >> Select the relevant type of KR. Below explained are the steps depending on the type of key result being selected. Based on the selected KR type, different fields are displayed. Below is the list of those fields based on the KY are KR types they are applicable to - Applicable to | Field name | Description |
---|
Metric, To do, Jira issues (via JQL) | Title | Title of the key result | Metric, To do | Owner | Select users user who is supposed to own the key result | Metric, To do | Start and Due date | Start and Due date of the key result. It should be between start and end date of the objective. | Metric | Behavior | Depends on how you want to track number in the metric Increase/Decrese - When number is supposed to be tracked that increases or decreases, use this behavior. E.g. Increase adoption rate by 10% or Decrease the hiring cost by 10$ 100$ for each recruit. Numbers can be of any unit like percentage, currency, etc Original value is current number and the Target value number is the number one wants to achieve and defines the success of the metric Maintain - When the given numbers being tracked in metric are supposed to be maintained, use this behavior. E.g. Maintain the NPS score at 8 X for the current quarter Original value is current number and the Target value range (min-max) is the ideal range that defines the number is being maintained | Metric, To do | Progress calculation | There are three ways to calculate the progress Manual - Users manually update the KR progress Jira issues - KR progress is tracked based on Jira issues based on the selected aggregate function and the custom field Note |
---|
In Progress calculation settings, Jira issues option is not applicable To do type of KRs |
Other Key Results - Jira issue progress tracked based on other KR’s progress Read Key result Behavior and Progress calculation (Manual/Automated) for more details about all progress calculation configurations. | Metric, To do | Description | KR description that has relevant KR-related information | Metric, To do | Reminders | To make sure users are consistently updating the progress of KRs and set the KR reminders that are sent automatically on set frequency like weekly, bi-weekly, monthly, etc. Read how to enable/disable KR reminders. |
Once above feilds fields are defined click on Save. The below Below image shows the Metric and To do type KRs added in objective. Jira issuesIn UpRaise, Jira Issue KRs provide a seamless integration between objectives and specific tasks or issues tracked in Jira. This integration allows for a more detailed and granular tracking of progress toward objectives. Search for issue with relevant JQL or with issue id, key, etc., and click on Search. Select one moe Jira issues (each Jira issue is added as a separate KR when multiple issues are selected), click on Next
Below screenshots shows the objective details where selected Jira issues are now added as KRs. Jira issues (via JQL)Jira Issues (via JQL) KRs provide a powerful way to align objectives with specific tasks or issues in Jira using Jira Query Language (JQL). As Jira issues meet the defined JQL, they are automatically associated with the given objective in UpRaise. This ensures that the progress is always up-to-date. Based on their progress, KR’s progress will be automatically tracked and its impact will be updated in objective’s progress automatically. Tip |
---|
#BestPractices If new to UpRaise and just rolling out OKRs, we recommend using default weightages. Once the understanding of the system and the calculation is clear, play around the weightages by tweaking them as needed and set different weights of KRs. |
|