Use cases for Jira Cloud integration

The information that contributes to your key results will sometimes live in other systems. So, we built the Jira Cloud integration for key results to eliminate 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 give you the option to dynamically populate the key results based on the issues returned by the JQL.

💡

Tip

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.

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.

__________________________________________________________________________

Examples of key results linked to Jira:

1️⃣  Issue Progress - Percentage example

  • 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

2️⃣  Issue Progress - Numerical Value example

  • 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)

3️⃣  Ticket Count - Numerical Value example

  • 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 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, or perhaps add a project management/agile coach key result as well. Objectives are commonly a collaborative effort between all members of the team.

Was this article helpful?
2 out of 2 found this helpful