The information that contributes to the completion of OKRs sometimes lives in systems other than 15Five— which is why we built the Jira Cloud integration. 15Five's Jira Cloud integration works alongside our Objectives feature to automatically update your team's key results in 15Five as Jira issues are updated, eliminating the duplication of work between 15Five and Jira. The ultimate goal is for Engineering, IT, Product, and any other team that uses Jira to provide visibility to the rest of the organization, without added maintenance.
We know that not all Jira issues are ready and assigned at the same time you are setting your objectives, so we allow you to dynamically populate key results based on the issues returned by the JQL.
In this article, you will learn...
Access and availability
⛔️ Required access to create or edit objectives.
👥 This article is relevant to people with permission to create and edit objectives.
📦 This feature is available in the Perform, Legacy Focus, and Total Platform pricing packages.
Note
Refer to our "Link a key result to a Jira Cloud issue" article for a walkthrough of linking key results.
Examples of key results linked to Jira
With our integration, you can track by either IssueProgress or TicketCount. When tracking issues by Issue Progress, we recommend tracking the key results with the Percentage or Numerical Value metrics. When tracking issues by Ticket Count, it’s best to track the key results with the Numerical Value metric.
Key results linked to Jira issues are only a piece of the overall objective. In these examples, we’d likely have both Product Management and Product Design add key results, likely around go-to-market strategy and customer validation, and maybe even add a project management/agile coach key result. Objectives are commonly a collaborative effort between all members of the team.
- Objective title: Bring 15Five into the Flow of Work with a deeper Slack Integration
-
KR title: All tickets are ready for Early Adopter program by June 15th
- Current Value = 67% , Target Value = 100%
- JQL: "Epic Link" = ENG-123 AND "Epic Link" = ENG-456 AND "Epic Link" = ENG-789
- Issue Progress: Update key result when issues are in which status = Beta Testing
- Objective title: Bring 15Five into the Flow of Work with a deeper Slack Integration
-
KR title: All Epics have shipped by June 30th
- Current Value = 2 , Target Value = 3
- JQL: "Epic Link" = ENG-123 AND "Epic Link" = ENG-456 AND "Epic Link" = ENG-789
- Issue Progress: Update key result when issues are in which status = Done (2 Epics are Done)
- Objective title: Bring 15Five into the Flow of Work with a deeper Slack Integration
-
KR title: All blocker and critical bugs have been fixed before public release on July 10th
- Current Value = 8, Target Value = 0
- JQL: "Epic Link" = ENG-123 AND "Release priority" = "Blocker for customer release" AND status not in (Closed, Done)
Note
Key results should be concrete, specific, and measurable. They should describe how you will accomplish the objective and measure whether you are on track, behind, or at risk of achieving that objective. Learn more about the OKR Methodology.