Why and when to use an auto KR?
...
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
This page is about OKR for Jira Cloud. Using Data Center? Click here. |
...
...
...
...
...
...
...
...
...
How to create an auto KR?
...
How to Create an Auto KR
When adding a KR to an
...
existing
...
objective, select
...
As you can see, most of the fields are the same as with the Standard KR, but instead of setting a start value and desired value, you should connect Jira issues. Right now the only option is to connect them via JQL query. It means that the issue list will be always up-to-date with all recent changes and new issues matching the query will be added automatically to the KR.
After clicking on the “Define JQL query to connect issues” button, a window will appear with all of the issues on your instance. Type in desired JQL query that would match the issues you’d like to connect to the KR. If you’re not familiar wh JQL, here is a neat explanation of how to use it.
After typing in the query, click “Search”. You’ll get a list of all issues matching your query. If you click “Save”, the issues on the list will be attached to the KR.
...
After saving, you can see your query in the KR creation step and auto KR is ready to be added.
...
Using auto KRs
All auto KRs have a “sync” symbol next to them- both on the OKR overview and on their pages.
...
the Linked issues option.
Click Link issues to establish connections between your Key Result (KR) and relevant Jira issues.
You have two options:
Select manually – Search for an issue name or apply filters to narrow down available issues based on criteria such as project, issue type, or other relevant parameters. Utilize Jira Query Language (JQL) for more granular and specific searches.
Automated linking – Here, you can set up automation rules to link related issues to OKR automatically when certain conditions are met. Define filters based on Project, Issue Type, Parent, and more. Alternatively, use JQL for automated linking based on your criteria.
Create issues seamlessly within the app by clicking the Create issue button.
If you’re not familiar with JQL, check out the Atlassian documentation.
After configuring your linking preferences, confirm your choices by clicking Link issues.
The number of linked issues will appear in the Linked issues section. Click on the number to see all the linked issues and further edit them depending on your needs.
Don’t forget to save your configuration.
Using Auto KRs
All Auto KRs are marked with a "sync" symbol, visible on the OKR Overview and individual pages.
In the Status changes section of the Auto KR, you will see both your own status changes and automatic progress updates made by
...
the OKRobot bot.
...
In the Activity tab,
...
you'll find all activities
...
related to
...
KR's issues.
...
A new activity will be added whenever an issue is connected, disconnected, or its status is changed.
...
In the
...
Linked issues section,
...
you will find all the issues
...
linked to the KR,
...
and you have the option to edit them. You'll also see when the KR was last synced with Jira and
...
can manually trigger a refresh (in case you
...
made changes and want to see the results immediately).
Converting Auto KRs into manual KRs
Click the three-dots menu next to the Update button and select Convert to manual KR.
You will be informed about what will happen after you change the KR type. Confirm the conversion by clicking Convert.
Your KR is now manual, which means:
Connected issues will remain connected but won’t have an impact on the progress.
There won’t be any automatic progress updates.
Your start/desired value won’t change unless you change it manually.
Converting manual KRs into Auto KRs
Click the three-dots menu next to the Update button and select Convert to auto KR.
You will be informed about what will happen after you change the KR type. Confirm the conversion by clicking Convert.
Your KR is now automatic, which means:
Progress is calculated based on connected issues, along with the start and desired values.
Progress updates occur automatically following any status change in connected issues (synced every 5 minutes; manually trigger refresh by clicking Trigger refresh in the Linked issues menu).
If issues are linked and if you have used JQL to link them, they are integrated into the JQL used for syncing matching issues. Modify the query to cover additional issues by clicking Edit linked issues button in the Linked issues section.
If you didn’t have any linked issues, you need to link issues to see any progress. You can do that by clicking Edit linked issues button in the Linked issues section.