Jira issues / JQLs as KR actions
In UpRaise, Jira issues (or JQLs) can be linked as either key results or as key result actions. However, what is possible will depend on the configuration here Key result configurations. When enabled, Jira issues (or JQLs) can be linked as KR actions only in Metric and To do type KRs.
Jira issues as KRs vs KR actions
By default, UpRaise has the KR actions configuration turned off. Meaning, you won’t be able to link Jira issues to KRs as actions. You will need to turn on the corresponding config first.
There is one school of thought that says Jira issues are ‘tasks’ and should not be used as key results. For them, completing Jira issues does not necessarily lead to completing their key results. Thus, they are more inclined to link Jira issues as KR actions.
For some teams, completing Epics/Stories or other issue types will mean they are making progress on the objective. In which case, they will link Jira issues as KRs.
Some examples below -
Jira issues as KRs:
You can use Jira Issue KRs to track progress towards key project milestones. For example, if your OKR is to launch a new feature, you can create Jira issues for each milestone (such as development, testing, and deployment) and link them as Key Results.
Utilize Jira Issue KRs to address specific bugs or issues within your product. Assigning each bug fix as a Key Result ensures that the team prioritizes and tracks the resolution of these issues effectively.
Track the progress of marketing campaigns by creating Jira issues for campaign setup, execution, and analysis. These issues can be linked as Key Results, reflecting the milestones achieved towards the broader objective of campaign success.
Utilize Jira Issue KRs to manage the sales pipeline by tracking opportunities, leads, and conversions. Each stage of the sales process can be represented as a Key Result, ensuring visibility and accountability throughout the pipeline.
Jira issues as KR Actions:
When you have smaller tasks or action items that contribute to the achievement of a Key Result, you can use Jira Issue KR actions. For instance, if one of your Key Results is to increase website traffic by 20%, you can create Jira issues for tasks like optimizing meta tags, improving site speed, or implementing SEO strategies, and link them as KR actions.
Use Jira Issue KR actions to track ongoing process improvements or optimizations. For example, if your Key Result is to enhance customer satisfaction, you can create Jira issues for gathering customer feedback, analyzing pain points, and implementing necessary improvements, thereby linking them as KR actions.
If one of your key results is related to enhancing employee skills, create Jira issues for training sessions, workshops, or certifications. Linking these activities as KR actions enables you to measure progress towards the Key Result of skill improvement.
Implement process automation initiatives by creating Jira issues for identifying repetitive tasks, evaluating automation tools, and implementing solutions. These actions contribute to achieving the Key Result of streamlining operations and increasing efficiency.
Add Jira issue as a Key result action
Navigate to the relevant Metric or To do KR detail page. (in images, we have used an example of metric type KR).
Click on Add new in actions section.
Click on Jira issue >> Next.
Search for relevant Jira issues with the help of basic or advanced search.
Select relevant Jira issue/s that you want to add as KR action/s.
Click on Next & then Save.
In the image below, Jira issues are added as KR actions in actions section.
Key result actions do not have any impact on the progress of key results. Thus, you can notice even if the Jira issue is resolved (when it is a KR action), it does not impact the KR progress.
UpRaise panel on issue detail pages also surface this information about KR actions.
Jira issues as KR action via JQL
Follow the same steps explained above, only select Jira issue via JQL option on Add action pop-up.
Add the action Title and JQL to search for relevant issues.
Click on Save.
This is how the Jira issue as action via JQL looks like in actions section on KR detail page.
Any progress updates and Jira issue updates like Summary, Assignee, etc. are prevented based on settings under Kr confirguations. Read Key result configurations | Prevent Jira issue updates once the corresponding objective is Closed, Abandone... for more details.