# Playbooks in Jira Service Management: Resolve work faster with guided, automated steps Source: https://www.youtube.com/watch?v=RPm7e5C0N-E Recap page: https://rapidrecap.app/video/RPm7e5C0N-E Generated: 2026-02-19T19:34:20.273+00:00 --- ## Quick Overview Jira Service Management Playbooks integrate actionable, step-wise guidance with automations directly within work items, enabling teams to resolve issues faster, ensure consistent responses, empower responders, and improve auditability by tracking execution progress and output directly in the issue. **Key Points:** - Playbooks provide actionable, step-wise guidance combined with automations directly in the work item context to help teams resolve items faster and with clearer guidance (0:07). - When guidance is external, teams face uncertainty about next steps, steps are not actionable, progress tracking is difficult, and reviewing past actions is hard (0:10). - The two primary roles interacting with Playbooks are the On-call Agent/Responder (Jordan), who follows defined playbooks, and the Project Admin (Alex), who defines and creates them (1:31). - Playbooks consist of Instructional steps (guidance) or Automation Rule steps (actionable automation) that can be configured in Space settings (3:07). - Automation steps execute defined rules, such as fetching data from New Relic or running an Azure runbook, with execution logs and output visible within the playbook steps (2:20). - Playbook creation involves defining steps, selecting step types (Instructional or Automation Rule), and setting conditions (filters using JQL, Status, etc.) to control when the playbook appears (3:00, 3:22). - Jira Service Management offers pre-built Playbook templates for common scenarios like 'High CPU on Amazon RDS' and 'Major Incident response plan' to help teams get started quickly (3:38). ![Screenshot at 00:36: The Jira Service Management interface showing an open incident ticket \('CPU Usage more than 80%'\) where the 'Playbooks' section displays available guided steps like 'New Relic: CPU Usage Crash Resolution' directly within the work item context.](https://ss.rapidrecap.app/screens/RPm7e5C0N-E/00-00-36.jpg) **Context:** This video introduces Playbooks within Jira Service Management, a feature designed to solve the common problem where procedural guidance and necessary actions for resolving work items (like incidents or service requests) are scattered across external documents or tools. The presentation highlights how integrating this guidance directly into the Jira issue streamlines resolution, improves consistency, and provides better tracking of execution by linking steps to automation rules. ## Detailed Analysis Playbooks in Jira Service Management deliver actionable, step-wise guidance with integrated automations directly within the context of a work item, accelerating resolution times and improving response consistency. The core problem addressed is when guidance lives outside the issue, causing agents to be unsure of next steps, wasting time context-switching, and making progress tracking difficult. Playbooks solve this by consolidating data, actions, and documents. Two key roles interact with this feature: Jordan, the On-call Agent/Responder, follows the playbook steps during execution, and Alex, the Project Admin, defines and manages these processes. Playbooks are built from steps, which can be either 'Instructional' (providing guidance) or leverage an 'Automation Rule' (executing actions). These automation rules can integrate with third-party systems like New Relic or Azure. When Jordan executes a playbook, like the 'Billing Service Outage Resolution Playbook,' the steps show success status, duration, and provide access to execution logs and the output of any automated steps, ensuring full auditability. Project Admins like Alex create these playbooks in Space settings, defining the steps and setting conditions (using filters like Work type, Status, or JQL) to determine when a playbook becomes visible on an issue. Furthermore, Jira provides several pre-built Playbook templates across IT Operations and ITSM categories, such as 'High CPU on Amazon RDS' or 'Provision software license,' which users can customize or extend to fit their specific organizational needs. ### Challenges Without Guidance - Teams are unsure what to do next - Steps are external and not actionable - Progress tracking is hard - Reviewing history is difficult (0:10) ### Role Interactions - Jordan (On-call Agent/Responder) follows defined Playbooks and takes action - Alex (Project Admin) defines processes and creates Playbooks for team members (1:31) ### Playbook Structure - Playbooks are step-by-step guides combining guidance and action - Steps can be Instructional (guidance) or Automation Rule (actionable automation) (3:07, 3:12) ### Execution and Auditing - During execution, steps show status (e.g., Success) and duration - Automated steps display 'Action details' and output logs for full auditability (2:20, 2:33) ### Playbook Configuration (Admin View) - Admins define steps and configure visibility conditions using filters like Work type, Status, and JQL in the Playbook details section (3:22) ### Getting Started - Pre-built Playbook templates are available across IT Operations and ITSM categories (e.g., 'Major Incident response plan') for rapid adoption (3:38) ![Screenshot at 00:05: Initial screen showing an incident ticket in Jira Service Management with the Playbooks section open and listing available resolution guides.](https://ss.rapidrecap.app/screens/RPm7e5C0N-E/00-00-05.jpg) ![Screenshot at 01:08: Slide summarizing the five key benefits of Playbooks: Powered by Automation, Within Work Context, Helps Consistent Responses, Empower responders, and Faster resolution & auditability.](https://ss.rapidrecap.app/screens/RPm7e5C0N-E/00-01-08.jpg) ![Screenshot at 01:31: Slide detailing the two primary roles: Jordan \(On-call Agent/Responder\) who executes, and Alex \(Project Admin\) who defines Playbooks.](https://ss.rapidrecap.app/screens/RPm7e5C0N-E/00-01-31.jpg) ![Screenshot at 02:20: View of an active playbook execution showing the first step, 'Assign ticket to yourself,' marked as complete, and the second step, 'Get data from New Relic,' ready to run.](https://ss.rapidrecap.app/screens/RPm7e5C0N-E/00-02-20.jpg) ![Screenshot at 03:50: The Automation rule builder screen showing the configuration for a rule named 'Retrieve user details from Okta when manually triggered,' demonstrating how automation steps link to external services.](https://ss.rapidrecap.app/screens/RPm7e5C0N-E/00-03-50.jpg)