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 (for example "Jira") and copy the URL. It starts with
https://chat.googleapis.com/. - Open Jaylert in Jira. Settings (⚙) → Apps, then Jaylert 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 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.
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 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 uses space webhooks instead, so nobody has to sign in to Google.
- Install Jaylert 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.
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 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 runs entirely on Atlassian Forge. It sends only what your rules select to the spaces you configure, and stores rules, encrypted webhook URLs and a 30-day delivery log (no issue content, no personal names) in Atlassian's Forge storage. Details: Privacy policy.