What notifications Jira offers
Email. The project's notification scheme decides who gets emailed about which events. By default, the reporter, the assignee and the watchers of an issue get the email. An admin can add recipients, such as the project lead or a group of testers, in the project settings under "Notifications."
Personal settings. Everyone picks which emails they want in their Jira profile, for example turning off emails about their own changes.
Push notifications in the mobile app. The Jira app notifies you about issues where you're the reporter, assignee or a watcher, and about mentions.
Filter subscriptions. Jira can email a saved JQL filter on a schedule, for example a list of the project's open bugs every morning.
Messages in your team chat. Jira sends an event to the team chat through a system webhook or an automation rule. Slack and Microsoft Teams have ready-made apps, and other team chat apps receive events through a webhook.
Why team events belong in a chat
Only the people on the issue get the email. A new bug has no assignee yet, so everyone else sees it only when they open the board. A tester won't know an issue is ready for testing until the developer tells them. A message in the chat reaches the whole team the same minute, and a developer can pick up the bug without waiting for someone to forward the link.
The people who talk to customers hear about releases last. A version ships in Jira, and support and sales learn about the new feature from a customer's question. When a bot posts the release to a chat they're in, they know about the changes on release day.
Discussions drift into direct messages. A developer checks details with a tester in a DM, and a designer sends a mockup there too. A month later, a new developer can't find out why the payment button moved to another screen. When the issue is discussed under the notification in a shared chat, the issue, the questions and the decision sit in one place, next to the rest of the team's work.
How to send Jira events to a chat
Team chat apps receive events through an incoming webhook. An incoming webhook is an address Jira sends a request to when an issue is created, its status changes or a version is released. The chat app posts the event as a message in a chat. In Jira, you enter this address in a system webhook or in a project automation rule, and choose which issues to send there.
Which events to send to the chat
Send the events a developer, tester or support agent needs to act on. If the bot posts every description edit, people will start skimming the chat the way they skim email.
New bugs and urgent issues. The bot posts to the team chat as soon as an issue is created. Only send the project, issue type and priority you need.
Status changes. When an issue moves to "Testing," the bot tells the testers. When it moves to "Review," it tells the reviewers.
Releases. When a version is released in Jira, the bot posts the version number, its description and a link to the issue list to the "[Company] Releases" chat. Support and sales can answer customers about the changes without asking developers.
[Company] Releases
48 members
Builds and deployments. Build and deployment results usually come from CI: in GitLab and GitHub Actions, you add a request to the incoming webhook address to the deploy step. Send monitoring alerts to a separate chat, as in the use case "How do you alert on-call engineers about outages?"
How to set up Jira notifications in Pachca
In Pachca, the incoming webhook belongs to a bot. The bot posts the event to every chat it's been added to, and you pick which issue fields go into the message in the bot's template. No code required. Pachca has ready-made integrations for GitLab and Grafana: the GitLab bot posts pushes, build and deployment results, comments and issues, and you set it up with the Help Center guide.
1. Create a bot. In "Integrations," choose "Bots" and click "Create bot." Name it after the project, for example "Jira · App," and add the Jira logo. On the "Incoming Webhook" tab, copy the Webhook URL.
2. Add the bot to a chat. A chat admin or the chat creator can do this. Open the chat settings, click "Add members" and go to the "Integrations" tab. The bot posts to every chat it's in, so create a separate bot for each stream of events. Give the notifications chat a prefix, for example "[Bot] Jira · App," so it stands out in the chat list.
3. Paste the Webhook URL into Jira and set up a message template with the issue fields in the bot settings:
**New bug {{issue.key}} · {{issue.fields.priority.name}}**
{{issue.fields.summary}}
Assignee: {{issue.fields.assignee.displayName}}
[Open in Jira](https://your-company.atlassian.net/browse/{{issue.key}})
4. Test it. Create a test issue or move an issue to the right status. The bot will post a message to the chat. If nothing arrives, check that Jira has the right address and the bot is in the chat.
For more on templates and the request format, see the webhook guide in the Help Center and the developer guide.
How to discuss an issue in the chat
Discuss in the thread under the notification. A thread is a discussion branch under a specific message. Questions about the bug, screenshots and logs stay under the bot's message, and the chat itself holds only notifications.
Bring in people who aren't in the chat. Pachca has cross-chat threads: with an @mention you can bring a designer or an analyst into the thread, even if they're not a member of the chat.
Thread
[Bot] Jira · App
Reproduced on Android 14: after returning from the bank app, the app never gets the payment status. Logs are attached to the issue.
can you look at the error screen? Right now users don't know what to do next
I'll make a version with a "Retry payment" button and post it here by tonight
Agree on reactions. For example, 👀 means "looking into it" and ✅ means "fixed." Reactions show whether anyone has picked up the bug, so nobody has to post about it.
Move the outcome into the issue. Once the thread reaches a decision, add it as a comment in Jira. The decision stays with the issue, and anyone who opens it later will see it.
Mute the chat if you only need it for reference. Click the bell in the chat. You'll still get mentions and urgent messages.
If you need direct notifications and replies in Jira
An incoming webhook posts the event to a shared chat. To message the assignee directly, mention them or create a Jira issue right from the chat, you need a bot that works with the team chat app's API and Jira's API. In Pachca, there are three ways to do this.
No code, in n8n. The Jira node in n8n starts a workflow when an issue is assigned to someone, and the Pachca node sends them a direct message. For how n8n works and how to connect Pachca to it, see the use case "How do you automate routine work with n8n and AI agents?"
Commands from the chat. A bot can create a Jira issue with a /task command or post the day's issues with /today. This takes a developer: Pachca sends messages with commands to an outgoing webhook, and the developer's program creates the issue through the Jira API.
Through Albato. Jira is one of more than 250 services you can connect to Pachca through Albato without code.
Setup for Yandex Tracker and Kaiten is similar. See the articles on Yandex Tracker and Kaiten.
Where to start
Start with one chat and one event: new high-priority bugs. After a week, look at how many messages came in and how many got a response. If the bot posts more often than the team can read, narrow the JQL filter. Then add releases to a chat for support and sales.
Frequently asked questions
Yes, Jira Data Center has system webhooks too. You set them up in the administration section. The Jira server needs internet access to send a request to Pachca's Webhook URL.
One Webhook URL accepts up to 10 requests per second. If someone changes a hundred issues at once, Jira sends a hundred events, so exclude bulk edits with a JQL filter.