Topic
- Workflow Automation & Efficiency
Featured Apps
Table of Contents
Overview
Ops and support managers often create runbooks and checklists for incident handling or routine tasks. While Jira issues can capture these as plain text, and Confluence is often used for detailed SOPs, the lack of structure makes execution harder to follow.
With Excel-like Tables for Jira, teams can turn Jira tickets into actionable runbooks with structured tables.
Scenario: Creating a Runbook or Checklist Inside a Jira Ticket
Jira native
- Checklists can be written in the description or stored in Confluence SOPs.
- Assigning ownership or deadlines requires multiple manual steps.
With Excel-like Tables for Jira
- Add a structured checklist with Task, Owner, Deadline, Done, and Notes columns.
- Use Jira field mapping to connect table values (e.g., Deadline to Due Date).
- Keep Confluence as the source of detailed runbooks, while ETJ makes the Jira issue actionable.
Value
Ensures runbooks are not only documented but also actionable in Jira, bridging SOPs in Confluence with execution in tickets.
