Jira issue via JQL KR allows you to add multiple Jira issues or epics as one KR. These KRs are synced with a JQL, where once the JQL is saved, system auto updates the list of those related issues in the objective.
This feature will allow you to create one KR that contains multiple Jira issues or epics. Progress calculation of such KRs will be done on the basis of progress calculation configurations set by UpRaise admins.
Add a correct JQL for relevant Jira issues/epics you want to add as KR
Add weightage of the KR against the main objective
Click on save.
Once saved, you'd see the KR added in your objective. If you click on the KR title, system navigates you the Jira search issue page with search results according to the JQL you have added while creating Jira issue KR via JQL.
Although Jira issues are connected with the objective as Jira issue KR (Via JQL), the respective objective will not be visible to all Jira issue assignees. The reason being that one might add 1000s of issues via JQL and the list will be dynamic, in such case, it isn't a good idea to update the shared with list every time.
How does the progress calculation work for Jira issue KRs via JQL?
In above image, all are Jira epics added in the KR. The image below shows how it looks like on the objective detail page when you save the KR.
When you click on the KR title here, 'All epics in the project UpRaise', system takes you to the Jira page where you can see issues/epics contained in this KR as per JQL query.
As mentioned above, depending on the key result configurations setting system would show you the progress percentage of the Jira issue (via JQL) KR.
When you add a Jira issue KR via JQL, system calculates the real-time progress% by default. When any changes happen in Jira issues statuses, system has to recalculate that progress. This job is run 4 times in a day (this is default setting, you can change the job frequency from OKRs >> manage tab ). However, mouse over on the KR allows you to use the refresh option (refresh icon in image above) this triggers the progress recalculation job manually.
Let us say, we have added two epics in the Jira issue KR via JQL. One of the epics has no issues or subtask in it, whereas another has 2 issues in it. Refer the image below to understand the calculation of progress calculation.
As per this image, A Jira issue KR contains two epics hence, system considers each of the epics progress contribution as 50% (100 divided by number of issues/epics within KR ). Same goes for the progress contribution from each issue within epic or subtask within Jira issue. Here, Epic 2 has two Jira issues within it hence each issue holds 25% progress contribution towards epics progress (total progress contribution of an epic divided by Number of issues, here 50/2 = 25% each).
So when one of the Jira issue has its resolution as 'Not empty' the progress would be considered as 25% for the entire Jira issue KR. If both the Jira issues had a resolution as not empty then the progress of the KR would have 50%.
Difference between Jira issues as KRs and Jira issues as KR via JQL
Jira issue as KR/actions
Jira issues as KR/actions via JQL
You can add only one Jira issue or epic as KR at a time
You can add multiple Jira issues or epics as one KR.
When you click on KR title, you are navigated to the Jira issue detail page
When you click on the KR title, you are navigated to the search issue page along with a list of Jira issues as per JQL.
Progress calculation of the Jira issues or epics is in real time for the first time and recalculated after daily one time job. No option to refresh, you need to wait until system recalculates the data.
Progress calculation of the Jira issues or epics is in real time for the first time and recalculated after a daily job that is 4 times in a day. Or it can be run manually at any time.
When Jira issue is added as KR, the objective is shared and made visible to Jira issue assignee.
When Jira issue is added as KR via JQL, the objective is not shared or made visible to Jira issue assignee/s.