How to Integrate Jira with Slack: Complete Step-by-Step Guide (2026)

Development teams lose hours every week context-switching between Jira and Slack. Someone updates an issue in Jira — but the rest of the team doesn’t know until they manually check. A bug gets marked Critical — but the team lead doesn’t find out until the next standup.

The Jira-Slack integration solves this. When configured correctly, your Slack workspace becomes a real-time command center for your Jira projects — notifications, updates, and actions all flow into the channels where your team is already working.

This guide walks you through the complete setup in 2026, plus use cases, advanced tips, and how to avoid the most common mistakes.

What the Jira-Slack Integration Does

Before setting it up, understand what the integration actually gives you:

• Real-time notifications in Slack when Jira issues are created, updated, commented on, or transitioned
• Work item previews — paste a Jira link in Slack and it automatically unfurls with key details (status, assignee, priority, description)
• Personal Jira notifications — get your Jira @mentions and assignments delivered as Slack DMs instead of email
• Slash commands — create Jira issues, search for issues, and check project status directly from Slack
• Subscription management — subscribe specific Slack channels to specific Jira projects or filters
• AI-enhanced summaries — with the newer AI integrations, get plain-English summaries of issue activity

Prerequisites

Before you start, make sure you have:

• A Jira Cloud account (this guide covers Jira Cloud — not Jira Server/Data Center which has a different integration method)
• A Slack workspace where you have admin privileges
• An Atlassian account with access to your Jira site
• Project admin rights on the Jira projects you want to connect

Step-by-Step: How to Set Up the Jira-Slack Integration

Step 1: Install the Jira Cloud App in Slack

1. Open your Slack workspace in a browser or the desktop app
2. Click Apps in the left sidebar (or go to More > Apps)
3. In the search bar, type “Jira Cloud”
4. Click on the Jira Cloud app published by Atlassian
5. Click Add to Slack
6. Slack will ask you to authorize the app — review the permissions and click Allow

The Jira Cloud app is now installed in your Slack workspace.

Step 2: Connect Your Atlassian Account

After installing, open a direct message with the @Jira bot in Slack. The bot will prompt you to connect your Atlassian account.

1. In any Slack channel or DM, type /jira connect
2. A message will appear with a Connect your Jira site button — click it
3. You’ll be redirected to Atlassian’s authentication page
4. Log in with your Atlassian account credentials
5. Enter your Jira site URL (e.g., yourcompany.atlassian.net)
6. Click Allow to grant the integration access to your Jira projects
7. You’ll be redirected back to Slack with a confirmation that your account is connected

Note: Each person who wants personal Jira notifications in Slack needs to complete this step individually.

Step 3: Connect a Jira Project to a Slack Channel

Once your account is connected, you can subscribe specific Slack channels to specific Jira projects. This is how your team gets project-level notifications.

1. Navigate to the Slack channel where you want Jira notifications (e.g., #engineering-sprint or #project-alpha)
2. Type /jira subscribe in the channel
3. A settings panel will appear — select the Jira project you want to subscribe
4. Choose the events that should trigger notifications:
5. Issue created
6. Issue updated
7. Issue transitioned (status changed)
8. Comment added
9. Issue assigned
10. Sprint started / completed
11. Deployment (if using Jira with CI/CD)
12. Optionally, add filters to narrow notifications (e.g., only notify for issues with priority = Critical, or only for a specific component)
13. Click Save

Your channel will now receive notifications from that Jira project.

Step 4: Configure Notification Preferences

To prevent notification overload, configure exactly which events matter to your channel:

1. Type /jira manage subscriptions in the channel
2. You’ll see all active subscriptions for that channel
3. Click Edit on any subscription to adjust which events trigger notifications
4. Use Filters to add JQL (Jira Query Language) rules — for example: priority = Critical AND status != Done

Recommended starting configuration for a dev team channel:
– ✅ Issue created (for new bugs and tickets)
– ✅ Issue transitioned to “In Progress”, “In Review”, “Done”
– ✅ Issue priority changed to Critical or Blocker
– ❌ Comment added (too noisy — keep this off for busy channels)
– ✅ Sprint started / Sprint ended

Step 5: Enable Personal Notifications

For individual team members who want to receive their own Jira notifications in Slack (instead of email):

1. In Slack, open a DM with @Jira
2. Type /jira notifications or click Manage notifications from any Jira message
3. Turn on the notification types you want:
4. When you’re @mentioned in a Jira comment
5. When an issue is assigned to you
6. When an issue you’re watching is updated
7. When your issue’s status changes
8. These will arrive as direct messages from the Jira bot

This replaces email notifications for most developers — keeping your inbox cleaner.

Using Slash Commands: Jira From Slack

Once the integration is set up, your team can interact with Jira directly from Slack using slash commands. No need to switch tabs.

Create a Jira Issue from Slack

/jira create

A form will pop up in Slack where you can fill in:
– Project
– Issue type (Bug, Story, Task, Epic)
– Summary
– Description
– Assignee
– Priority
– Labels

Click Create and the issue is created in Jira immediately.

Shortcut: You can also hover over any Slack message and use the Create Jira Issue option in the message actions menu — the message text auto-fills the issue description. This is perfect for turning a Slack conversation about a bug directly into a tracked Jira ticket.

Search for Jira Issues in Slack

/jira search [search term]

Returns matching Jira issues without leaving Slack. You can click through to open the full issue in Jira.

Check Your Assigned Issues

/jira my issues

Lists all Jira issues currently assigned to you, with status and priority.

Transition an Issue Status

Some versions of the integration allow you to transition issue status directly from Slack notification messages — look for the Move to… buttons that appear on issue notification cards.

Advanced Configuration: Filtering With JQL

One of the most powerful features of the Jira-Slack integration is the ability to use Jira Query Language (JQL) to filter exactly which issues trigger Slack notifications.

Example JQL filters for Slack subscriptions:

Only notify for Critical priority bugs in the current sprint:

priority = Critical AND issuetype = Bug AND sprint in openSprints()

Only notify for issues assigned to your team:

assignee in membersOf("backend-team")

Only notify when high-priority issues are created:

priority in (Critical, Blocker) AND status = "Open"

Exclude certain issue types from notifications:

issuetype not in (Sub-task, Epic) AND status changed

To apply a JQL filter to a subscription:
1. Type /jira manage subscriptions in the channel
2. Click Edit on the subscription
3. In the JQL Filter field, paste your JQL query
4. Click Save

This dramatically reduces notification noise while keeping your team informed of what actually matters.

Use Cases: How Different Teams Use Jira + Slack

Use Case 1: Engineering Team Standup Channel

Setup: Subscribe #eng-standup to your active sprint’s Jira project with filters for status changes only.
Result: Every time a ticket moves to “In Progress”, “In Review”, or “Done”, it automatically appears in the standup channel. Daily standups become faster because everyone can see movement in real-time.

Use Case 2: Critical Bug Alert Channel

Setup: Create a #critical-alerts channel. Subscribe to all Jira projects with JQL filter: priority in (Critical, Blocker) AND issuetype = Bug
Result: Any time a Critical or Blocker bug is created or escalated anywhere in the company, the team is alerted immediately — no manual escalation required.

Use Case 3: Client Project Channel

Setup: For each client, create a Slack channel (e.g., #client-acme-project). Subscribe to the relevant Jira project with notifications for key transitions (In Review, Ready for Client, Done).
Result: The account manager gets real-time updates on deliverable progress without needing to check Jira manually.

Use Case 4: Sprint Ceremony Notifications

Setup: Subscribe #eng-sprints to sprint events (sprint started, sprint ended, sprint goal updated).
Result: The whole team is automatically notified when a sprint kicks off and when it ends, with sprint metrics linked.

Use Case 5: Creating Issues from Slack Conversations

Setup: Train your team to use the “Create Jira Issue” message action.
Result: When someone says “Hey the payment button is broken” in Slack, the on-call engineer right-clicks the message, selects “Create Jira Issue”, and a properly filed bug ticket is created in seconds — without leaving Slack.

Common Issues and How to Fix Them

Notifications not appearing in the channel:
– Verify the subscription is active: /jira manage subscriptions
– Check that your JQL filter isn’t too restrictive
– Confirm the Jira Cloud app hasn’t been removed from the workspace

“Not authorized” error when using /jira commands:
– Type /jira connect to re-authenticate your Atlassian account
– If you changed your Atlassian password recently, you’ll need to re-authorize

Link previews not unfolling:
– Go to Slack workspace settings and confirm “Show previews of websites” is enabled
– The Jira app needs to be in the channel where links are pasted

Too many notifications flooding the channel:
– Narrow your JQL filter to only include critical events
– Remove notification types that aren’t useful (comments are usually the biggest offender)
– Consider creating separate dedicated channels for different notification types

Duplicate notifications:
– Check if multiple subscriptions are covering the same project in the same channel
– Type /jira manage subscriptions to audit and remove duplicates

Jira + Slack AI Integration in 2026

The newest development in Jira-Slack workflows is AI-enhanced summaries. Atlassian’s Rovo AI and third-party tools like eesel.ai can be layered on top of the basic integration to provide:

• Natural language issue search: “What bugs were filed this week?” answered in plain English
• Sprint summaries: AI-generated daily or weekly digests of sprint progress posted to Slack
• Automatic triage suggestions: When a new issue is created and posted to Slack, AI suggests priority, assignee, and labels based on past issue history
• Meeting summaries linked to Jira: AI connects Slack huddle recordings to related Jira tickets

These AI features are rolling out through Atlassian Intelligence and third-party integrations in 2026.

The Bottom Line

The Jira-Slack integration is one of the highest-impact productivity setups for any engineering team. When configured properly — with smart JQL filters, the right notification events, and personal notification preferences — it eliminates the constant tab-switching between Jira and Slack.

The setup takes about 30 minutes. The return on that 30 minutes is fewer missed updates, faster responses to critical issues, and a team that spends more time building and less time tracking.

Start with a single project subscription, get the notifications dialed in over a week, then expand to other projects.

Related Posts:
– Jira vs Monday.com 2026: Which Is Better for Dev Teams?
– How to Integrate Asana with Slack: Step-by-Step Guide
– Best Jira Integrations for Software Development Teams in 2026