The Jira Slack integration runs on one official app, Jira Cloud for Slack, which you install once and connect to your Jira site. After that you get issue previews inside conversations, channel subscriptions for project activity, personal notifications by direct message, and the ability to create or update work items without opening Jira.
I set this up for a development team, and the install is the easy part. The work that actually matters comes afterward, when you decide which channels hear from Jira and how loudly. This guide covers both, plus the connection and permission snags that show up once real people start posting issue links.
On this page
- What the integration actually does
- Before you start: permissions and admin approval
- Connect the apps
- Configure channel notifications
- Jira Data Center vs Cloud
- Troubleshooting
What the integration actually does
Jira Cloud for Slack pushes information into Slack in three distinct ways, and it helps to keep them separate in your head because you configure each one differently. Get this distinction right up front and the rest of the setup makes sense.
| Flow into Slack | What triggers it | How you set it up |
|---|---|---|
| Personal notifications | Activity on work items you are assigned, watching, or mentioned in | /jira notify in a DM with @Jira |
| Channel subscription | New and updated work items in a connected space, filtered by your rules | /jira connect, then tune with /jira manage |
| Issue previews (unfurls) | Someone posts a Jira link or an issue key | Automatic once the channel is connected to that space |
On top of those flows, you can act on a work item straight from the message: transition it, assign it, comment, or watch it using the buttons under an unfurled preview or the More actions menu. You can also create a work item with /jira create, and the Jira app’s Home tab in the Slack sidebar lists everything assigned to you or watched by you. It is a genuine two-way link, not just an alert feed.
Before you start: permissions and admin approval
Two things gate this integration, and both catch people out.
First, a Jira site administrator has to allow the connection. If the integration has been switched off at the site level, anyone trying to link a workspace sees the message “Connecting with this Jira Cloud instance was disabled by administrator.” The admin enables it from the Jira side at the Slack integration configuration page under your instance’s app administration. If you are not the admin, sort this out before you gather the team, or you will get stuck at the first click.
Second, permissions carry over from Jira. The app respects your existing Jira permissions at both the work item and administration levels, so a person in Slack only ever sees and interacts with work items they already have permission to access in Jira. That is a feature, not a bug, but it explains why two people can look at the same channel and see different previews.
One more thing worth knowing so it does not alarm you: when you first connect, the Slack workspace is given a Needs review status until a site admin approves it. You can configure and use Jira from Slack in the meantime, so that label is not blocking you.
Connect the apps
You can start this from the Slack side, which is what I recommend, since the app then walks you through linking Jira.
- Install the Jira Cloud for Slack app onto your Slack workspace. You can add it from the Apps section at the bottom of the Slack sidebar (search “Jira Cloud”), or from the Slack Marketplace and Atlassian’s install link.
- After installing, follow the prompt to log into your Atlassian account to link Slack and Jira. This takes about a minute.
- Once you have logged in, you get a direct message from the Jira Cloud app in Slack. From that DM you can connect your first Jira space to a Slack channel.
- If your Atlassian account is connected to more than one Jira site, you will be asked to select the site and then the space you want to connect.
That is the whole connection. The moment it completes, issue previews and the create and interact features start working for the people in that channel. Personal notifications and channel subscriptions still need their own setup, which is where most of the tuning happens.
Configure channel notifications
This is the section that decides whether the team keeps the integration or mutes it in a week. A channel wired to a busy space with default settings turns into a wall of updates nobody reads. Set it up deliberately.
Connect a channel to a space:
- In the public or private channel you want to use, type
/jira connect. Note that this does not work in direct messages with other Slack users; it has to be a channel. Inviting the @Jira bot into a channel also offers the same quick connect prompt. - Select the Jira site and space to connect. You will get a confirmation posted in the channel.
Tune what the channel actually receives:
- Type
/jira managein the connected channel, then select Manage to open the connection settings in Jira Cloud. - Configure the notification filters. Space admins can choose between a basic or extended notification format and apply JQL-based advanced filtering, which is the setting that saves you.
- Use the same
/jira manageview to pause notifications or disconnect a space when a channel gets retired.
The JQL filter is the difference between a useful channel and a noisy one. Rather than subscribing a squad channel to every change in a 400-issue project, scope it to what that squad owns, something like project = DEV AND priority in (High, Highest), and let the low-priority churn stay in Jira. You can also drive this from the Jira side: open your space’s settings, go to Notifications, and under Connect to Slack select Get started.
Set up personal notifications separately, per person, so individuals get their own assignments and mentions without subscribing a whole channel:
- Open a DM with @Jira, or any channel @Jira is in, and type
/jira notify. - Select Turn on personal notifications.
- Choose when you want to be notified and select Submit.
Once personal notifications are running in Slack, you can turn off the duplicate emails in Jira: select Settings, then Notification settings, and switch off the toggle next to Send me emails for work item activity. Receiving every notification twice is exactly the kind of thing that gets the whole integration blamed.
Jira Data Center vs Cloud
If you are on Jira Data Center rather than Cloud, this is a different app with a different setup, so do not follow the Cloud steps above. You install Jira Data Center for Slack from the Atlassian Marketplace, and Atlassian confirms the integration is fully compatible with Data Center. A few differences matter in practice:
- Your Jira instance has to be reachable over the internet through a secure HTTPS connection for Slack to talk to it.
- Setup involves a manual credential exchange: you generate credentials on the Slack side and paste them into the Jira configuration on the Data Center side.
- Data Center notifications cannot be sent into Slack direct messages or multi-party direct messages.
- It supports connecting to multiple Slack workspaces, which suits a Slack Enterprise Grid.
- Unfurling works with issue keys in upper or lower case on Data Center (
DEV-36ordev-36both trigger a preview), and there is a dedicated/jira_serverslash command for unfurling as well.
Troubleshooting
The connect step says the integration was disabled
If you see “Connecting with this Jira Cloud instance was disabled by administrator,” a site admin has not enabled the Slack integration for your Jira site. Ask them to switch it on from the Jira app administration settings. Separately, a new workspace showing a Needs review status is normal and does not block you; you can keep using the integration while a site admin approves the workspace.
Jira links or issue keys are not unfurling
The usual cause is a missing connection. The channel has to be connected to the relevant space with /jira connect before the bot will unfurl work items from it, so a DEV-36 posted in a channel that is not connected to the DEV space shows nothing. Connect the channel to the right space and post the link again.
The channel is drowning in notifications
Run /jira manage in that channel and open the settings in Jira Cloud. Narrow the subscription with a JQL filter so it only reports the issues that channel cares about, switch from the extended to the basic format if the cards are too heavy, or pause the connection entirely. This is almost always a filter problem, not a reason to remove the integration.
Someone cannot see a preview that others can see
This is permissions doing their job. The app only shows a person the work items they already have permission to access in Jira, so if a teammate cannot see an unfurled issue that you can, check their Jira permissions for that project rather than the Slack setup.
You cannot run /jira connect in a direct message
Channel connections are not supported in direct messages with other Slack users. Use a public or private channel for /jira connect, and handle anything personal through /jira notify in your DM with @Jira instead.
No personal notifications are arriving
Personal notifications are opt-in per user. Type /jira notify, select Turn on personal notifications, choose your timing, and select Submit. If you had earlier disabled Jira email notifications expecting Slack to take over, this step is the one that was missing.
Once the connection is stable and the filters are tuned, the integration mostly disappears into the background, which is the goal. If you are still weighing whether Jira is the right home for this workflow, it is worth checking Jira’s current pricing tiers against how many people actually need write access, and comparing it with the best Jira alternatives or a head-to-head like Jira vs Linear. If your team lives in a different tool, the same principles apply to Asana’s Slack integration, which handles channel notifications in a comparable way.
