Key Takeaways
- Integrating Jira Service Management with Slack brings incident response directly into the channels where teams already work, reducing context switching and speeding up triage.
- Teams can route alerts based on priority and manage incidents directly from Slack using interactive actions and /jsmops commands for acknowledgement, assignment, escalation, notes, and more.
- Two-way syncing keeps Slack conversations and JSM tickets aligned, helping responders maintain context without duplicating updates across tools.
- A well-designed ChatOps setup requires more than just connecting the tools. Alert routing, escalation policies, knowledge base quality, and governance all play a role in keeping workflows efficient and scalable.
Modern IT teams rely heavily on Slack for real-time collaboration and Jira Service Management for incident resolution. When alerts, on-call rotations, and service desk tickets live strictly inside JSM, context switching quickly becomes a bottleneck. Teams lose time toggling between tools, with response times stretching and critical alerts risk getting buried in email inboxes. Integrating Jira Service Management with Slack brings full ChatOps capabilities directly into your team’s daily communication hub. Whether you are managing high-priority incident triage, routine IT requests, or on-call schedules, connecting JSM and Slack ensures your team can resolve issues faster without leaving their active chat channels. Here is your complete guide on how to set up a Slack-JSM integration, why it matters for your support workflows, and a reference list of slash commands to supercharge your ChatOps.
Why Connect JSM and Slack? Key Benefits for Support & Ops Teams
Connecting Jira Service Management to Slack transforms passive alert channels into interactive incident response rooms.
Unified Incident Triage and Accelerated MTTR
Responders can acknowledge, snooze, escalate, or close alerts directly using interactive Slack buttons or slash commands. This eliminates login delays during critical P1/P2 incidents.
Intelligent Notification Routing
Avoid notification fatigue by setting up granular filters. Route high-priority (P1/P2) alerts to an urgent on-call response channel while funneling routine informational alerts to team-specific channels.
Frictionless Employee Support with the Atlassian Virtual Agent
- Self-Service Deflection: When employees ask questions in Slack, JSM’s AI Virtual Agent queries your Confluence knowledge base first. If an answer exists, it resolves the question instantly.
- Effortless Ticket Creation: If human intervention is needed, the Virtual Agent automatically opens a JSM ticket, or teammates can convert any Slack message into a ticket using emoji reactions (like 🎫 or ⚡).
- Two-Way Thread Syncing: Updates made in Slack threads sync back to the JSM ticket, and agent comments in JSM reflect immediately in Slack.
Simplified On-Call & Shift Management
Check who is currently on duty, swap shifts, or mute individual notifications directly within Slack, keeping engineering teams agile during off-hours.
JSM + Slack ChatOps Flow
How to Connect Jira Service Management and Slack
If you are looking to integrate Slack and JSM, you need the following prerequisites:
- You must have Jira Admin or Team Admin permissions in Jira Service Management.
- A connected Slack workspace with appropriate permissions to install the JSM ChatOps app.
- Pre-created Slack channels (public or private) or direct message threads designated for alert routing.
Step 1: Connect Your Slack Workspace to Jira
- Log in to your Atlassian account and navigate to Jira Service Management.
- Connect your Slack workspace to your Jira site following Atlassian’s workspace connection prompts.
- In your Slack workspace, verify the connection by running /connect in any channel.
Step 2: Add the Slack Integration in JSM
Option A: Team-Level Integration (Available on Free, Standard, Premium, and Enterprise Plans)
Use this option to receive notifications specifically for alerts where your team is designated as a responder.
- Navigate to your Team profile page in Jira.
- Scroll to the Operations section and click Go to operations.
- Select Integrations from the sidebar and click Add integration.
- Select Slack from the integration directory.
Option B: Site-Level Integration (Available on Premium and Enterprise Plans)
Use this option to capture site-wide alerts that do not yet have an assigned responder team.
- Go to Settings (gear icon) > Apps > Operations (or next to Operations in the sidebar, select More actions … > General configuration).
- Click Integrations > Add integration.
- Select Slack from the list.
Step 3: Configure Integration Settings & Alert Filtering
- Name the Integration: Give it a clear, descriptive label (e.g., DevOps-P1-Alerts or IT-Support-Triage).
- Assign Responder Team & Workspace: Select the associated team and target Slack workspace.
- Choose Slack Channel or DM: Click Select on Slack, choose your destination channel, and click Allow to confirm permissions.
- Tune Action Buttons & Fields: Configure whether interactive action buttons appear on messages and choose which alert fields display.
- Set Up Filters: Define custom filters so the channel only triggers on relevant alerts (e.g., filter by Priority = P1/P2 or specific tags).
- Click Continue. Your integration is now ON by default.
Note on Resetting: Slack workspaces and channels cannot be directly swapped inside an existing integration. If you need to change destination channels later, open the integration, select More actions … > Reset, and re-run the configuration.
Jira Service Management Slack Command Reference
Once connected, your team can execute on-call and alert management actions directly in Slack using /jsmops slash commands:
