he same Slack channel and the same hour of Jira activity under three subscription settings: every event as 22 messages, a JQL filter as 9 messages, and an hourly digest grouped by issue as 1 message.

‍

‍

Why do Jira email notifications get missed?

Jira email is one person's feed of everything they ever touched. A watch set in March, a comment on a ticket reassigned in June, and today's P1 arrive with the same subject shape from the same sender, so after a week the Jira filter gets muted and the one assign that mattered goes with it. Email also has no room to act: you can read that a status changed, but you cannot transition or reassign without leaving the inbox. Slack fixes both problems, provided the stream stays readable. A channel that mirrors every event in a project is a louder inbox with a different logo.

The rest of this page is about keeping the stream readable: what Atlassian's own app gives you, how to scope notifications to one person or one channel, how mentions work, how Troopr's subscription model differs, and how to keep a busy project from turning its channel into a firehose.

How do I set up Jira notifications in Slack?

Atlassian's Jira Cloud for Slack app handles personal and channel notifications, and personal ones are on by default the moment you connect your Atlassian account. Set the official app up first, and add Troopr afterwards if a channel needs more control than the app gives you.

Personal notifications with /jira notify

Open a DM with @Jira, or any channel the bot has joined, and type /jira notify. Pick Essentials or All. Essentials covers work assigned to you, mentions, comments on your work items, and status changes on items you watch, which is the right default for almost everyone. Narrow further by space, work type, or priority if you need to. Each DM shows the title, status, priority, assignee, and what changed, with actions on the card.

Channel notifications with /jira connect, and from Jira space settings with JQL

In the channel, type /jira connect, choose the Jira site and space, then filter by work item type, priority, and event type. For anything the picker cannot express, start from Jira: open the space, choose More actions, then Space settings, then Notifications, and under Connect to Slack select Get started. Space admins can choose a basic or extended card format there and add JQL-based advanced filtering. Later, /jira manage in the channel lists every subscription with options to update its filters, pause it, or disconnect the space.

Everything above is Jira Cloud. Self-hosted teams use Atlassian's separate Slack for Jira Data Center app for notifications, and Troopr connects to Jira Cloud and Jira Data Center on every plan.

Turn Jira email off once Slack works

Atlassian recommends this itself, so repeat it to your team. Once Slack is receiving personal notifications, open Jira Settings, then Notification settings, and switch off "Send me emails for work item activity." Two copies of every assign is how people end up muting both.

Which Jira notifications belong in a channel, and which belong to a person?

The split that keeps both streams readable is simple. Anything about your own work is a personal notification: assigned to you, a mention, a comment on an item you reported or watch. Anything the whole team needs to see at the same moment is a channel notification: a new bug in the project, a status change on the board, a sprint starting or closing. When a channel subscription carries personal events, everyone reads everyone else's assignments and the channel gets muted. When personal DMs carry project-wide events, the person gets the whole project in their inbox and the DM gets muted.

Set channel subscriptions for team events with a filter tight enough that each message is worth reading, and let personal notifications carry the rest. Troopr enforces the split from its side too: if a channel you belong to already carries an event, you do not get the DM for it as well.

How do I get Jira notifications for only my tickets?

This is the question behind the top-ranking community thread, and the answer depends on the app.

With the official app, do not try to make a shared channel personal. /jira notify with Essentials already limits your DMs to work assigned to you, mentions, comments on your items, and watched items, and a space filter narrows it further. A channel subscription belongs to the whole channel.

With Troopr, run /t configure in your Troopr DM and choose Personal notifications. Turn on any of assigned to me, watched by me, and reported by me, or replace the toggles with a personal JQL filter such as assignee = currentUser() AND priority in (Highest, High). Add event and field filters when only some changes matter, and switch off self-actions so your own edits never ping you. Delivery is real time or batched, in standard or compact format. If a channel you belong to already carries the same event, Troopr skips the DM rather than telling you twice.

How do I turn Jira notifications off in Slack?

The second community thread on the results page asks exactly this, and there are five levers.

• Run /jira notify again to narrow what triggers a DM: switch from All to Essentials, or add a space, work type, or priority filter. The prompt sets what arrives, not whether anything does.
• Run /jira manage in the channel to pause or disconnect a subscription.
• /jira logout signs you out but leaves channel subscriptions running, so it is not an off switch for the channel.
• Mute the @Jira DM in Slack, which is Atlassian's own route to silence for personal notifications, or mute the channel when the subscription is right for the team and wrong for you.
• On the Troopr side, every notification footer carries a preferences link, and a channel admin can pause, edit, or delete a subscription from /t configure without losing its settings.

Troopr also posts a short transparency message in the channel whenever someone configures alerts there, so nobody has to guess where a stream came from.

How do Jira mentions work in Slack?

A mention is the notification people least want to miss and most often lose in email. In Slack, the official app's Essentials set includes mentions, so a DM from @Jira arrives whenever someone @-mentions you on a work item.

Troopr treats mentions as their own class. "Always send updates where I am mentioned" bypasses every other personal filter, including a JQL filter that would otherwise exclude the ticket. A Slack member an admin has mapped to a Jira account receives mention DMs before they have verified their own Jira login, so new joiners are covered from day one. In the message, Jira mentions render as Slack display names with avatars, and Jira comment markup converts to Slack formatting. A mention DM is not sent when the person cannot see the project in Jira, because Troopr never shows anyone a work item their permissions hide. Mentions in the same batching window arrive as one message rather than a pile.

How does Troopr handle Jira notifications in Slack?

Troopr is the AI project management agent for engineering teams. It reads the team's real Jira, GitHub and Slack activity, forms its own view of what is happening, and does the coordination that would otherwise fall to a manager, including keeping Jira current through changes the owner confirms. Notifications are one of its plainer jobs, and the reason they are worth a section is the subscription model underneath them.

Any Slack channel can carry any number of subscriptions. Each one covers one or more Jira projects, and one project can feed several channels with different rules, so #bug-triage and #engineering can watch the same project and hear completely different things. Every subscription has four parts, and every part is set independently.

Events you can subscribe to

Issue created, issue updated, comment created, comment updated, sprint started and sprint closed. A subscription can carry any combination, so a release channel can hear about sprints and nothing else, and a triage channel can hear about new issues and nothing else.

Filters: JQL, changed fields and status transitions

Three filters, all on the same subscription. A JQL query, validated against Jira as you type it, so a typo fails in the editor rather than silently matching nothing. A changed-field filter, so an update fires only when a field you care about moved. And a status transition condition, from any status or a specific one to a specific status, which is how a channel hears about a Bug moving into Triage and nothing else about that Bug. The three stack, so "Bugs at High or Highest, when status moves to Triage" is one subscription rather than a compromise.

Delivery: real time or batched, grouped by issue

Real time, or batched every 1, 5, 15 or 30 minutes, or every 1, 2, 4, 6 or 12 hours. A batch groups its events by issue and pages when it is long, so twenty transitions at standup arrive as one message that reads as a list of issues, each with what changed, rather than twenty cards. Duplicate suppression covers retries and mirrored events, so a change that Jira reports twice appears once.

Formats: standard, compact and detailed

Standard shows the card. Compact keeps the card small and puts the details in a thread, which is the right setting for a busy channel that still wants to see everything. Detailed puts fields and actions inline, which is the right setting for a triage channel where the next step is a click. Beyond the three formats you can truncate summaries, collapse the message, hide the card, show or hide the last update, and add a footer message.

A notification that opens a synced thread

A subscription can post each notification as a threaded message, or start thread sync on it, so a real-time notification becomes a live synced thread: replies in Slack post to Jira as comments as the person who wrote them, Jira comments and status changes post back into the thread, and files move both ways. The conversation about the bug happens under the bug and ends up on the ticket. The sync ends on its own when the issue reaches Done.

Sprint notifications with a velocity chart

Sprint start posts the board, the sprint, its duration and the committed story points. Sprint close posts commitment against completed and draws a velocity chart, so the retrospective has its first slide before anyone opens Jira.

Personal notification preferences

Personal notifications are evaluated on every event for the assignee, the reporter, watchers and mentioned people. You choose which of those relationships reach you, or replace the toggles with a personal JQL filter, and you can narrow further by event and by field. A self-actions toggle stops your own edits from pinging you. Delivery is real time, real time with a synced thread, or batched, in standard or compact format. Admins can set the defaults on behalf of newly verified users, and every notification carries a preferences link so nobody has to ask where the setting lives.

Emoji markers: the quieter signal

When a message is too much, a reaction on the source message is enough. Per channel you can mark the message when its issue is created, when it is done, when it is assigned, and when the message has sat unattended for five minutes. Done is detected from the statuses or resolutions you choose. The same markers are applied to real-time notification messages, so a glance at the channel shows which reports became tickets and which of those are closed.

Admin controls

A channel admin sets subscriptions from /t configure or from Channel Preferences in the web app, and can enable, pause, edit or delete each one. A transparency message is posted in the channel when alerts are configured. Every notification Troopr sends is written to a per-workspace notification log, and Jira user mentions inside them are translated to Slack display names. People without a Jira licence take part through guest facilitation, acting through an account the admin authorises and attributed to them. Notifications are not metered on any plan; Free covers them without limit.

How do I stop the channel becoming a firehose?

Tighten the JQL before you install a second app. Atlassian's space-settings filter can pin a channel to one board, one work type, or one priority band, and for many teams that is the whole fix.

When a tight query still produces a stream nobody reads, the problem is shape rather than volume, and this is where Troopr's subscription model does its work. Twenty transitions at standup become one grouped message. A #bug-triage subscription can fire only when a Bug moves into Triage, in real time and in detailed format, opening a synced thread on each one so the conversation lands on the ticket. Every issue in a notification keeps its triage buttons, and every action runs as you through your own Jira connection. The whole two-way surface, including channel sync and Task It, is on the Slack Jira integration that syncs both ways.

The last lever is not a notification at all. A routine in Troopr Routines is a standing instruction in plain language, and any routine can be set as a watch: it checks on its schedule and posts only when its condition is true. "Tell me if anything in the sprint has been In Review for more than two days" says nothing on a good week. Silence is the signal, and the routine's last result still reads "checked, nothing to say", so a quiet watch is visibly working rather than visibly broken. Watch conditions include an issue count against a threshold, the sum of a numeric field against a threshold, issues not updated in a number of days, and any JQL. At Yahoo, managers on the process-automation team got back about 3.8 hours a week of meeting logistics once coordination moved into Slack, and the unglamorous precondition for that is channels nobody has muted.

What can't the official Jira Slack app do with notifications?

Credit where it is due: the official app notifies well, filters with JQL from space settings, and puts actions on the card. The gaps are specific, and there are four.

No digest.

Every event is its own card. There is no interval that turns an hour of transitions into one message.

No status-transition condition on the subscription.

You can filter by type, priority, event, and JQL, but you cannot say "only when a Bug moves from Open to Triage" on the channel's subscription itself.

A notification does not become a synced thread.

The card lets you comment, transition, assign, or watch. It does not open a thread whose replies post to Jira as comments.

The return path is thin.

Atlassian documents thread sync as Slack replies becoming Jira comments. Troopr's synced thread mirrors comment edits and deletions, attachments, formatting, and mentions in both directions, posts a change line when a status or field changes in Jira, and lets each channel set the direction: two-way, Slack to Jira only, or Jira to Slack only.

That is the complete list for notifications. The full comparison, including creation, custom fields, and guests, is on Troopr vs Jira Cloud for Slack.

What should each channel subscribe to?

Start with fewer events than you think and add on request; removing a subscription people have learned to ignore is harder than adding one they asked for. Where the bug report itself starts in Slack, the thread can become the ticket, and how to create a Jira ticket from Slack covers every method.

Why are my Jira notifications not showing up in Slack?

Six causes cover almost every case.

The person has not verified their Jira account. Troopr sends personal notifications to people it can map to a Jira account. Mention DMs reach mapped-but-unverified users; assigned, watched and reported notifications need the person to connect Jira from the App Home, the launcher or the web app. An admin can send verification reminders to one person or a whole channel.

The event is already covered by a channel. If a channel you belong to carries the event, Troopr skips the DM by design. Check the channel before assuming the DM failed.

The subscription's JQL excludes the issue. The filter is validated for syntax, not for intent. Run the same query in Jira and see whether the issue is in the result.

The webhook is not registered. Troopr registers Jira webhooks for created, updated, comment and sprint events when the connection is made, and shows a status card with a copyable URL, an event checklist and a Verify button for the manual path. If the card shows events missing, add them in Jira.

The person cannot see the project in Jira. Troopr never shows anyone a work item their Jira permissions hide, so a notification about a restricted project does not arrive. That is the permission model working.

Delivery is batched. A subscription or a personal preference set to every hour will hold the event until the window closes. The count in the batch header shows what it is waiting on.

Can Jira send notifications to Microsoft Teams?

Yes. Atlassian's Jira Cloud app for Microsoft Teams sends personal notifications to your chat with the app, where typing Notifications sets and adjusts them, and channel notifications once the app is added to a team or channel and you run @Jira Notifications, filtered by space. You can also start from Jira: your avatar, then Notifications, then Space and work item notifications. Jira Automation's Send Microsoft Teams message action posts rule-driven alerts without the app.

Troopr runs in Microsoft Teams as well as Slack, delivering standups, routines, and proposals into team channels. The subscription controls on this page are Troopr's Slack surface.

‍

Frequently Asked Questions

Does Jira integrate with Slack?

Yes. Atlassian's Jira Cloud for Slack app, which is free, connects a Jira Cloud site to a Slack workspace for notifications, previews, creation, and card actions. Troopr is a second layer on top: batching, per-channel JQL and transition filters, notifications that open as synced threads, and Jira activity mirrored back into Slack.

How do I add notifications in Slack?

For Jira, type /jira notify in a DM with @Jira for personal ones, or /jira connect in a channel for the team's. With Troopr, run /t configure in the channel, choose Notification Settings, and add a subscription with events, filters, delivery, and format.

How to set up Jira notifications?

Personal notifications are on by default once you connect your Atlassian account in Slack; /jira notify changes what triggers them. For a team, connect the channel with /jira connect or from Space settings, then Notifications, then Connect to Slack. Then turn off "Send me emails for work item activity" in Jira so nothing arrives twice.

How do I get Jira notifications in a Slack channel?

Type /jira connect in the channel and pick the space, or start from the space's settings in Jira for JQL filtering. With Troopr, run /t configure in the channel and add a subscription: choose the project, the events, a JQL or status-transition filter, the delivery interval and the format.

Can Jira send notifications to Teams?

Yes, through Atlassian's Jira Cloud app for Microsoft Teams, which handles personal and channel notifications, and through Jira Automation's Send Microsoft Teams message action. The steps are in the section above.

Can I get Jira notifications in Slack without Troopr?

Yes. Install Jira Cloud for Slack, keep the default personal notifications, and connect your project channel. Troopr is the layer you add when the stream needs batching, transition filters, or a thread that stays synced with the ticket.

How do I stop missing Jira email notifications?

Move them. Put personal notifications in Slack DMs, put project events in the project channel behind a tight filter, and disable Jira's work item emails. If the channel still floods, batch it and filter by status transition.

What is the difference between official Slack notifications and Troopr?

Both deliver personal and channel notifications with actionable cards and JQL filtering. Troopr adds delivery intervals from one minute to twelve hours with grouping, a status-transition condition on the subscription, compact or detailed formats, a synced thread spawned from the notification, and a two-way return path that carries edits, deletions, and files.

Can I filter Jira Slack notifications with JQL?

Yes, in both apps. The official app takes JQL from Space settings, then Notifications, then Connect to Slack. Troopr validates a JQL filter on each channel subscription and on personal notifications, and combines it with changed-field and status-transition filters.

Why am I not getting Jira notifications in Slack?

Usually one of six things: the account is not verified with Jira, a channel already carries the event so the DM is skipped, the subscription's JQL excludes the issue, the Jira webhook is missing an event, the person cannot see the project in Jira, or delivery is batched and the window has not closed. The troubleshooting section above walks through each.

Do Troopr notifications replace email?

For work item activity, yes, once you have confirmed the Slack stream is arriving. Keep Jira email for anything Slack is not subscribed to, and do not run both at full volume.

Can a notification start a Slack thread that stays on the Jira issue?

With Troopr, yes. Set the subscription to start thread sync, and each notification opens a thread where replies become Jira comments and Jira comments post back. The sync ends on its own when the issue reaches Done.

Is there a free way to get Jira notifications in Slack?

Yes, twice over. The official app is free. Troopr's Free plan covers 10 seats with every feature, and channel and personal notifications are not metered on any plan.

What Slack command lists my Jira issues?

In Troopr, /t list, scoped to the channel's default project or board, with filters for assigned, reported, watched, and more. In the official app, /jira KEY previews one work item privately and the Home tab lists your assigned and watched work.

Do you need Troopr for this?

If the official app's DMs and one filtered channel already give you a stream people read, stop here and turn off the email. If the channel still floods after a tight JQL, or you want the notification to be the place the work finishes, Start for Free and add one subscription to your busiest channel. That is the whole test.

‍