Setup takes about two minutes. You need to be a Jira administrator and a member of the Google Chat space.
https://chat.googleapis.com/v1/spaces/.If you don't see webhooks, your Google Workspace administrator may have turned them off, or you are using a personal Gmail account. Webhooks are only available on Google Workspace accounts.
The webhook URL is stored encrypted in Atlassian's Forge storage. It is never shown again on the settings page. Anyone who has the URL can post to the space, so treat it like a password.
A newly connected space receives every event from every project. Click Edit filters to narrow it down:
| Filter | What it does |
|---|---|
| Projects | Only issues from the selected projects. Empty means all projects. |
| Events | Issue created, issue updated, comment added, issue assigned. None selected means all. |
| Only status changes | For updates, send a message only when the status changes. Other edits are ignored. |
| Only when the status changes to | For updates, send a message only when the issue moves to one of the selected statuses, for example Done to hear only about finished work. Empty means any status. |
| Issue types | Only the selected issue types, for example Bug. Empty means all types. |
| Fields that send an update | Which field changes send an "Issue updated" message. Any field works, including custom fields such as Sprint or Story points. Empty means status, assignee, priority, summary and resolution. |
| Also show on the card | Up to 10 more fields to print on every card from this space, for example Due date, Sprint, Story points or Labels. Empty fields are left out. |
| JQL | Only issues that match the query, for example labels = customer AND priority in (High, Highest). Jira checks the query when you save it. |
| Notify everyone (@all) | Pings everyone in the space when an issue is created with, or raised to, one of the selected priorities. |
| Combine quick changes | Off by default. When on, updates wait one minute; everything that changed in that minute goes out as one message. If a field changes several times, the card shows the first and last value. If several issues change (a bulk edit), one card lists them all. |
| Ignore Automation | Changes made by Jira Automation rules and other apps are not sent. |
| Include restricted content | Off by default. When on, issues with a security level, comments restricted to a role or group, and internal notes in Jira Service Management are sent too. Everyone in the space will see them. |
You can connect several spaces, each with its own filters. For example, bugs from the WEB project can go to the support space while every status change goes to the team space.
A digest sends the result of a JQL query to a space at a set time, for example open bugs every weekday at 09:00 or overdue issues every Monday.
The card lists up to 20 issues with status, priority, assignee and due date, highest priority first unless the query has its own ORDER BY, and says how many more match. Digests arrive within the hour you choose. By default nothing is sent when no issues match. Issues with a security level are left out unless the space includes restricted content.
Anyone on the site can get notifications about their own work, without an admin setting up a rule for them.
Changes you make yourself are never sent to you. The card says why you got it, for example "You are the assignee". If an issue is taken off you, you get one last message ("You were the assignee"). Before every message the app asks Jira whether you can see the issue. Issues with a security level and restricted comments are never sent to personal spaces.
Admins can turn personal notifications off for the whole site on the app's settings page. This also stops the ones already set up.
Project administrators can connect Google Chat spaces for their own project, without asking a Jira admin.
A project space only receives issues from that project, and restricted content is never sent to it. Jira admins see these spaces on the main settings page, where they can edit or remove them, and can turn project spaces off for the whole site. Turning it off keeps the spaces already connected.
By default, updates to other fields, such as description, labels or rank, don't send a message. Add them under Fields that send an update. For long text fields such as Description the card says "Edited" instead of showing the text.
Each connected space on the settings page shows when its last message was sent. If the last message failed, it shows the error and what to do about it.
The Delivery log at the bottom of the settings page lists the last 50 messages: sent, failed with Google's error, or not sent because the issue or comment is restricted or the space's JQL has an error.
Copy the full URL from Google Chat. It must start with https://chat.googleapis.com/v1/spaces/ and contain key= and token=.
The webhook was deleted in Google Chat, or the space no longer exists. Create a new webhook in the space, then click Change URL on that space in Jira and paste the new URL. Filters, digests and the alert setting stay as they are.
Check the space's filters and the delivery log. Also check that the changed field is listed under Fields that send an update. Restricted issues and comments are not sent unless the space allows it, and Jira doesn't send the app events for content the app isn't allowed to see.
Jira usually delivers events within seconds, but it can take longer when Jira is busy. If Google Chat rate-limits the space, the app waits and retries.
If a webhook was deleted, or you want to replace one (for example after it was shared by mistake), create a new webhook in the same space and click Change URL next to the space in Jira. The app sends a test message to the new URL and only saves it if Google Chat accepts it. Filters, digests and the alert setting stay as they are. Then delete the old webhook in Google Chat.
Click Remove next to the space. Jira stops sending to it and the stored webhook URL is deleted. The webhook itself stays in Google Chat; delete it there if you no longer need it.
Still stuck? Contact support.