Jira Slack Integration 2026: Setup, @Jira Tickets and Channels Without the Noise
The Jira Slack integration is one official app, Jira Cloud for Slack. Install it in your Slack workspace, log in to your Atlassian account, and you can create Jira work items from any message, get personal notifications in DMs, subscribe channels to a Jira space, and edit work items from live preview cards. Since June 2026 you can also type @Jira in a channel and ask for a ticket in plain language, as long as your organization has Rovo turned on.
Installing takes a few minutes. The part that decides whether your team keeps it is what comes after: which channels hear from Jira, and how much. Most of the complaints I hear about this integration are really complaints about one channel subscribed to an entire busy space.
I implement work-management tools through SSPM, a Smartsheet Premier Aligned Partner, and Slack is where most of those tools end up talking to people. Every step below is checked against Atlassian’s Jira Cloud for Slack documentation as of October 7, 2026. This covers Jira Cloud. Data Center is at the end.
What the integration does
Think of it as three flows into Slack and three ways to act on Jira from Slack.
Into Slack:
- Channel subscriptions post updates from a connected Jira space into a channel. Set up with
/jira connect, managed with/jira manage. - Personal notifications arrive as DMs from @Jira about your assignments, mentions, comments on your work items and status changes on items you watch. They’re on by default once you connect your account.
- Link preview cards appear when someone pastes a Jira link, or types a work item key like
DEV-36in a channel connected to that space. The card shows live status, priority, assignee and description, and you can edit fields inline.
From Slack into Jira:
- Create a work item from a message with the message’s More actions menu.
- Use slash commands like
/jira createfor a quick form, or/jira DEV-36to look up a work item privately. - Mention @Jira to create, update, search or assign work in plain language.
There’s also a Home tab in the Jira app that lists what’s assigned to you and what you’re watching, and thread sync, which copies a Slack thread into Jira as comments.
Before you start
Two things block people at the first click.
A Jira site admin has to allow it. If the integration is switched off, anyone connecting sees “Connecting with this Jira Cloud instance was disabled by administrator.” The admin enables it at https://<your-site>.atlassian.net/plugins/servlet/ac/jira-slack-integration/addon-config-page. Sort this out before you gather the team.
Slack workspaces start as “Needs review.” That status sits there until a site admin approves the workspace, but it doesn’t block you. People can configure and use Jira from Slack in the meantime.
Also expect permissions to carry over. The app respects Jira permissions at both the work item and admin level, so people only see and act on work items they can already access in Jira. Work items under a security scheme don’t send Slack notifications at all.
Connect Jira and Slack
- Install Jira Cloud from the Slack Marketplace, or search “Jira Cloud” under Apps in the Slack sidebar.
- Follow the prompt to log in to your Atlassian account. That links Slack and Jira.
- You’ll get a DM from the Jira Cloud app. From there you can connect your first space to a channel.
- If your Atlassian account has more than one Jira site, pick the site, then the space.
- For private channels, invite @Jira to the channel first.
That’s the connection. Previews and create actions start working right away. Channel subscriptions and personal notification settings need their own setup, and that’s where the real work is.
Create Jira tickets from Slack
This is what most people searching for “Jira Slack integration” actually want: turning a Slack conversation into a ticket without copying and pasting. You have three ways to do it.
From any message
Hover over the message, select More actions, then Create work item from Jira Cloud. If Rovo is available, turn on Use Rovo to draft the summary and description from the message. In a channel, Rovo gets the whole thread as context; in a DM it only sees the one message you picked. Fill in the space and work type, then submit.
When you create a single work item this way, the Slack thread syncs to the work item’s comments automatically, so later replies land in Jira too.
With /jira create
Type /jira create to open a form with space, work type, summary and description. It’s predictable and works without Rovo, but it doesn’t auto-fill anything from the conversation.
With @Jira
Type something like @Jira create a bug for the login issue discussed in this thread. Atlassian’s @Jira guide says it uses the whole thread when you mention it in a thread, or the last 15 messages in the channel otherwise. If it has every required field, it creates the item and posts a link. If not, it asks.
The same @Jira can update work (@Jira change the priority of PROJ-456 to High), search (@Jira what are my open bugs in Marketing?), and assign work to a supported coding agent such as Cursor, GitHub Copilot or the Claude agent for Jira. Bulk actions on more than 10 work items ask for confirmation first.
Three things to know before you roll @Jira out:
- It needs Rovo. An organization admin has to activate Rovo in Atlassian Administration. Rovo comes with every paid Jira plan, with a monthly credit allowance per user.
- Set defaults per channel. The first @Jira in a channel asks for a site and a default space. Run
/jira agentto change them, and use the custom instructions field for your conventions, such as “bugs from this channel go in the PAY space with the label customer-reported.” - Search results respect access. If any result comes from a restricted space, only you see the answer, and you choose whether to post it to the channel.
Atlassian announced @Jira in June 2026. If your team already uses Rovo heavily, check how this fits your credit allowance, especially after metered billing starts December 3, 2026. Our Atlassian fall 2026 pricing guide explains the Rovo credit meter.
Set up channel notifications that people read
A channel subscribed to a busy space with default settings becomes a wall of updates nobody reads. Then someone mutes it, and then everyone does. Set it up on purpose.
Connect from Slack:
- In the channel, type
/jira connect. This works in public and private channels, not in DMs with other people. - Choose the site and space.
- Set filters for work item type, priority and event type.
- Select Confirm.
Or connect from Jira, which gives space admins more control: open the space, select More actions (•••) next to its name, then Space settings, Notifications, and under Connect to Slack select Get started. Here admins can choose a basic or extended message format and use JQL-based advanced filtering.
JQL is what keeps a channel useful. Instead of every change in a 400-item space, subscribe the squad channel to what it owns:
project = DEV AND priority in (High, Highest) AND statusCategory != Done
Or route customer-facing bugs to support:
project = DEV AND type = Bug AND labels = customer-reported
If you’re rusty on the syntax, our JQL advanced filters guide has patterns you can copy.
My defaults for a team rollout:
- One channel per team, connected to that team’s space. Not one #jira channel for the whole company.
- Basic format for busy channels. Extended cards are fine for a low-volume release or incident channel.
- Status changes and new high-priority items only. Leave comment chatter in Jira and in personal notifications.
- Review after two weeks. Run
/jira manageand tighten anything people complain about. You can also pause a subscription or disconnect a retired space there.
Tune personal notifications
Personal notifications are on by default once you connect. To adjust them:
- Open a DM with @Jira (or any channel the bot is in) and type
/jira notify. - Pick Essentials (recommended) or All. Essentials covers assignments, mentions, comments on your work items and status changes on items you watch.
- Add optional filters by space, work type or priority, then select Submit.
Then switch off duplicate emails in Jira: Settings, Notification settings, and turn off Send me emails for work item activity. Getting every update twice is the fastest way to get the integration blamed. Atlassian’s notifications guide has the full list of options.
Troubleshooting
“Connecting with this Jira Cloud instance was disabled by administrator”
A site admin hasn’t enabled the Slack integration. They can turn it on at the add-on configuration page shown above. A workspace showing “Needs review” is a separate, normal status and doesn’t block you.
Work item keys don’t turn into previews
Two common causes. The channel has to be connected to the space the key belongs to, so DEV-36 shows nothing in a channel that isn’t connected to DEV. And keys need to be typed in uppercase. Pasting the full Jira link works either way.
Someone can’t see a preview that others can
That’s permissions working. The app only shows people the work items they can access in Jira. Check their Jira permissions for that space, not the Slack setup. If they don’t have Jira access at all, the app offers to invite them or request access from an admin.
No Slack notifications for certain work items
If those items use a work item security scheme, Jira doesn’t send Slack notifications for them. That’s by design.
The channel is drowning
Run /jira manage, open the subscription and add a JQL filter, switch to the basic format, or pause it. It’s almost always a filter problem, not a reason to uninstall. If notifications are missing or late everywhere, not just in Slack, see our Jira notifications troubleshooting guide.
@Jira doesn’t respond
Check that Rovo is activated for your organization, that the Jira app has been added to the channel (Slack requires that before anyone can talk to it), and that /jira agent has a site and default space set.
You can’t run /jira connect in a DM
Channel subscriptions don’t work in DMs with other people. Use a channel for subscriptions and /jira notify in your DM with @Jira for personal alerts.
Jira Data Center
None of the Cloud steps above apply to Data Center. It uses a separate integration, and Atlassian has a migration path from the legacy Jira Server integration for Slack to Jira Cloud for Slack. Keep the timeline in mind: Atlassian stopped selling new Data Center licenses on March 30, 2026, and Data Center reaches end of life on March 28, 2029. If you’re still on Data Center, plan the Slack setup as part of your cloud migration rather than rebuilding it twice.
Where this fits
Once channels are filtered and personal alerts are on Essentials, the integration mostly fades into the background, which is the point. If you’re planning a Jira rollout, check Jira’s current pricing against how many people actually need access, since Slack users who interact with Jira still need Jira access. And if part of your company works in Asana, our Asana Slack integration guide follows the same “fewer, better notifications” approach.
FAQ
Is the Jira Slack integration free?
The Jira Cloud for Slack app costs nothing to install. You need a Jira Cloud site, and the people who interact with Jira need Jira access. Jira’s Free plan covers up to 10 users. The @Jira natural-language features need Rovo, which comes with paid Jira plans.
How do I create a Jira ticket from Slack?
Hover over a message, select More actions, then Create work item from Jira Cloud. You can also type /jira create for a form, or mention @Jira and describe the ticket in plain language if Rovo is turned on.
How do I stop Jira from spamming a Slack channel?
Run /jira manage in the channel, open the subscription and add a JQL filter so the channel only gets the work items it owns. Switching to the basic message format and limiting event types also helps. Space admins can set this from the space’s Notifications settings in Jira.
Why aren’t Jira issue keys unfurling in Slack?
The channel must be connected to the space the key belongs to, and keys need to be typed in uppercase. Pasting the full work item link always triggers a preview card.
Can I sync a Slack thread to a Jira ticket?
Yes. On a link preview card, select Sync with thread and confirm. All earlier messages and every new reply are added as comments on the work item until you unsync it.
Setup steps and feature details checked against Atlassian Support’s Jira Cloud for Slack documentation and Atlassian’s June 24, 2026 @Jira announcement on October 7, 2026.
Sponsored
