Overview

Quantive Results enables you to integrate with Jira in several possible ways. Use the Quantive Results plugin for Jira Cloud or Server/ Data Center to link your Jira items to Quantive Results Objectives and show the work that you're actually doing in Jira to support your OKRs.

If you're after building powerful insights and automating your Key Results with data from your Jira instance, use the Quantive Results Jira integration. This article provides an in-depth description of both integrations and the use cases they cover.

The Quantive Results plugin for Jira Cloud or Server/ Data Center is a native plugin that you add to your Jira instance. It enables you to create a link between a Jira item and a Quantive Results Objective, and it works the following way:

This integration helps you visualize better in Jira and in Quantive Results, what work you are doing towards a specific Objective. For example, I have an Objective to deliver a Quantive Results Zapier app. I track these items as separate Tasks, but since Jira is the system where all Engineering work is tracked, I also have to track them as issues under a specific Epic. In order to avoid duplication of work, what I’ve done is, I’ve logged all these in Jira, and I’ve linked them to the Zapier all Objective in Quantive Results. So now everyone that is interested in how the Zapier app is going, can go in Quantive Results, see my Objective and see these Tasks.

The plugin uses the Quantive Results API to pull all objectives and present them for selection when you use the plugin's UI. It also uses the Quantive Results API to create a corresponding Task in Quantive Results. Finally, to keep the Jira item and Quantive Results Task statuses in sync, it uses a WebHook, that you have to set up in Jira, and it talks to Quantive Results to make the status updates.

Unlike the Jira plugin, the Quantive Results Jira integrationis set up in your Quantive Results account. It enables you to pull selected Jira data in the Quantive Results Data warehouse and specify how frequently (hourly, daily, weekly..) this data must be refreshed.

You then have this data at your disposal, so you can create insights in your Quantive Results account. An insight enables you to specify some business logic using our Codeless Insights editor (or via SQL and HTML for the more advanced scenarios). An insight typically outputs a value, corresponding to the business logic you specified for it. You can use this value to automatically update your Key Results and KPIs in Quantive Results.

Instead of going in and manually updating your KRs/KPIs every cadence, if this data lives in Jira you can set things up so that the numbers from your Jira insights update your KRs/KPIs automatically. For example, I'm working on an Epic in Jira and I track all my work there. This Epic directly represents one of my Key Results this Q - to add Quantive Results Zapier integration. I want to measure the Epic progress based on the number of completed issues and have that progress update my Key Result in Quantive Results. For this, I have connected Quantive Results to our Jira instance and I have built an insight that measures the completed items / all items under this Epic. I have configured my Key Result to track progress automatically based on this insight's number.

Technically speaking, when I set up a Jira data source connection in Quantive Results, I grant Quantive Results permission to sync the content I select from Jira. Quantive Results requests this content using secure JDBC or REST API requests. When I create an insight, I'm querying the copy of my Jira data in the Quantive Results Data warehouse. Each time the Jira data source synchronizes, it pulls the latest data from the Jira instance. After a successful sync, all insights, that use this data source are prompted to re-calculate. Since each insight keeps a reference of all the KRs/KPIs that use its value to update their progress automatically, after the insight finishes recalculation it updates the KR or KPI with the new value.