Quick start
You need to be a Jira administrator and a member of the Google Chat space.
- Create a webhook in Google Chat. Open the space, click the space name, then Apps & integrations → Webhooks → Add webhook. Name it Jaylert Chat and, as the avatar URL, use
https://jaylert.com/assets/avatar.pngso messages show the Jaylert Chat logo. Save and copy the URL. It starts withhttps://chat.googleapis.com/. - Open Jaylert Chat in Jira. Settings (⚙) → Apps, then Jaylert Chat in the left menu.
- Create a rule. Click New rule, name it, paste the webhook URL, choose projects and events, and click Save rule.
- Send a test message. Click Send test message on the rule. A sample card with your selected fields appears in the space.
Google Workspace admins can turn off incoming webhooks for their organization. If the space has no Webhooks option, ask your Workspace admin.
Rules
Each rule posts to one Google Chat space. You can have up to 50 rules, for example one per team.
| Setting | What it does |
|---|---|
| Name | Shown in the rule list and the delivery log. |
| Webhook URL | The Google Chat space to post to. Stored encrypted; afterwards only its end is shown. Leave it empty when editing to keep the current one. |
| Projects | Only issues in these projects. Empty means all projects. |
| JQL filter | Only issues matching the query, e.g. priority in (High, Highest) AND labels = customer. Combined with the project filter. |
| Events | Issue created, status changed, assignee changed, priority changed, comment added. |
| From status → To status | For status changes only: notify on a specific transition, e.g. any status → Done. |
| Show on the card | The fields on the message card (see below). |
| Enabled | Turn a rule off without deleting it. |
If several rules match the same event and point to the same space, Jaylert Chat sends one message.
What the card shows
Always: the issue key, summary and type, who made the change, what changed, and an Open in Jira button.
Per rule, you choose from: status, assignee, priority, reporter, due date, labels, components, fix versions, the first 300 characters of the description, and the first 300 characters of a new comment. Empty fields are left out.
All messages about one issue go to the same Chat thread. Comments with restricted visibility and internal notes in Jira Service Management are never sent; the card only says a comment was added.
Daily digest
Instead of a message for every event, a rule can send one card a day. Under Delivery, choose Daily digest, the hour and your time zone. With Weekdays only, weekend updates arrive in Monday's digest.
The digest groups updates by issue: the latest summary, then each change in order, with an Open button. Up to 30 issues are listed; the card says how many more there were. Days without updates send nothing.
Project admins
Project administrators can manage notifications for their own project without Jira admin rights: Project settings → Jaylert Chat. Their rules always apply to that project only, and they see only their own rules and deliveries. Jira admins see every rule on the site, with project rules marked.
Delivery log and retries
The Delivery log tab lists the messages of the last 30 days, newest first.
- Sent: Google Chat accepted the message. Sent (2nd attempt) means it went through on a retry.
- Retrying: Google Chat had a temporary problem (rate limit or server error). Jaylert Chat tries again after 30 seconds, then 2, 5 and 15 minutes, up to 5 attempts.
- Failed: the message could not be delivered, with the error shown. A wrong or deleted webhook is not retried.
Moving from Google Chat for Jira Cloud
Google's app connects each space to Jira through the Chat app. Jaylert Chat uses space webhooks instead, so nobody has to sign in to Google.
- Install Jaylert Chat and create one rule for each space you used before, with the same projects.
- Use Status changed with a To status (for example Done) instead of all updates, and add a JQL filter to keep only what the team needs.
- Send a test message from each rule.
- When the new messages arrive, remove Google's app from the space (Apps & integrations) to avoid duplicates.
Who can do what
| Role | Where | Can |
|---|---|---|
| Jira administrator | Settings (⚙) → Apps → Jaylert Chat | Create, edit, test and delete every rule on the site, including project rules; see the full delivery log. |
| Project administrator | Project settings → Apps → Jaylert Chat | Manage rules for their own project only; see deliveries of those rules. The project filter is fixed to their project. |
| Everyone else | Google Chat | Read the messages in the spaces they belong to. Nothing to install or connect. |
Limits
| What | Limit |
|---|---|
| Rules per Jira site (site and project rules together) | 50 |
| Description and comment excerpt on a card | 300 characters |
| Issues listed in one daily digest | 30, then "and N more issues" |
| Daily digest queue | 7 days (e.g. a long weekend) |
| Delivery attempts on temporary Google errors | 5 (after 30 s, 2, 5 and 15 minutes) |
| Delivery log | 30 days |
| JQL filter length | 2,000 characters |
Google Chat also limits how fast one space accepts messages. Jaylert Chat sends one message per matching event (or one digest a day) and retries automatically when Google asks it to slow down.
Uninstalling
Remove Jaylert Chat under Settings (⚙) → Apps → Manage apps. Rules, encrypted webhook URLs, the delivery log and any queued digest updates are stored in Atlassian's Forge storage for your site and are deleted by Atlassian after the app is uninstalled. Messages already posted stay in Google Chat; delete the space webhook there if you no longer need it.
Troubleshooting
| Problem | What to do |
|---|---|
| "This is not a Google Chat webhook URL" | Copy the full URL from the space's Webhooks screen. It must start with https://chat.googleapis.com/. |
| Test message fails with 404 or 400 | The webhook was deleted or the URL is incomplete. Create a new webhook and paste it into the rule. |
| No messages for some issues | Check the rule's projects, JQL, events and transition. Try the JQL in Jira's issue search. |
| "Retrying" in the log | Google Chat limits busy spaces. Jaylert Chat retries on its own; no action needed. |
| "License not active" | Renew the app or start a trial under Apps → Manage apps. Your rules are kept. |
Still stuck? Contact support.
Data and privacy
Jaylert Chat runs entirely on Atlassian Forge. It sends only what your rules select to the spaces you configure, and stores rules, encrypted webhook URLs, a 30-day delivery log (no issue content, no personal names) and, for daily digests, a short-lived queue of issue updates in Atlassian's Forge storage. Details: Privacy policy.