Install
Before you start
- Jira Cloud, any plan. Jira Data Center and Server are not supported.
- Google Workspace with Google Chat. Incoming webhooks must be allowed; personal Gmail accounts cannot create webhooks.
- A Jira administrator installs the app. Project administrators can use it afterwards for their own projects.
Install from the Atlassian Marketplace
- In Jira, go to Settings (⚙) → Apps → Explore more apps, and search for Jaylert Chat. You can also start from the app's Atlassian Marketplace listing.
- Click Try it free. The first 30 days are free, and sites with up to 10 users never pay.
- Review the permissions and confirm. Jaylert Chat asks to:
- read issues, comments, projects and statuses, to match rules and fill in the message card;
- read user names, to show who made a change;
- store its own data (rules, encrypted webhook URLs, the delivery log);
- send messages to
chat.googleapis.com, the Google Chat webhook address.
Where to find it
- Jira administrators: Settings (⚙) → Apps, then Jaylert Chat in the left menu, below the list of apps. The first time, Jira may show Allow access: Jaylert Chat checks with your own permissions that you are a Jira administrator. Click Allow access, then Accept.
- Project administrators: the project's Space settings (called Project settings on some sites) → Apps → Jaylert Chat. The first time, Jira may show Allow access: Jaylert Chat checks with that person's own permissions that they administer the project. Click Allow access, then Accept.
Updates
Updates install automatically. If an update ever needs a new permission, Jira asks an administrator to approve it under Apps → Manage apps; until then the previous version keeps working.
Quick start
After installing, you need to be a Jira administrator (or a project administrator, for your own project) 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 (see Where to find it).
- Create a rule. Click Add 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. A saved project that is no longer in the list (archived or deleted) is shown as "Project … (not in the list)"; remove it there. |
| JQL filter | Only issues matching the query, e.g. priority in (High, Highest) AND labels = customer. Combined with the project filter. The query runs for everybody's changes, so currentUser() can't be used; name the user or group instead. |
| 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. Statuses are matched by name too, so a rule also works in projects created later (for example a new team-managed project with its own "Done"). |
| Show on the card | The fields on the message card (see below). Applies to right-away delivery; the daily digest has its own compact format. |
| Also send issues with a security level | Off by default; only Jira administrators can turn it on (see below). |
| Enabled | Turn a rule off without deleting it. |
If several right-away rules match the same event and point to the same space, Jaylert Chat sends one message. Daily digest rules each send their own digest.
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, except status, assignee and priority: when chosen they always show (Unassigned or a dash when empty).
All messages about one issue go to the same Chat thread. The text of comments with restricted visibility and of internal notes in Jira Service Management is never sent. Jira may not notify apps about restricted comments at all; then no message appears for them.
Issues with a security level
An issue security level means only some people may see the issue, but everyone in a Google Chat space sees the message. So by default Jaylert Chat does not post issues with a security level; the delivery log says "Not sent: the issue has a security level" (at most once an hour per rule). If a space contains exactly the people allowed to see those issues, a Jira administrator can turn on Also send issues with a security level in that rule on the admin page. Project administrators see this setting but cannot change it.
Issues the app itself may not see (a security level or permission scheme without the atlassian-addons-project-access role) are never sent: Jira does not tell the app about them. If Jira does report a change but the app can't read the issue (for example it was deleted or its permissions changed in the meantime), the delivery log says "Jaylert Chat cannot read this issue".
Good to know: a comment added together with a status change (for example on a transition screen) gives two messages in the issue's thread, one per event. An issue moved to another project gets a new key, so its later messages start a new thread.
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 first digest arrives at the next chosen hour: a 09:00 digest set up in the afternoon starts the next morning.
The digest groups updates by issue: the latest summary, then its changes in the order they happened in Jira (the last 8; older ones are counted), with an Open button. Issues deleted before the digest is sent are left out; an issue moved to another project is listed with its new key. Up to 30 issues are listed (fewer if the card would exceed Google Chat's message size); the card says how many more there were. Days without updates send nothing. A very busy rule with more than 500 updates in a day sends a "500+ updates" card: it summarises the oldest 500, and the rest of that day's updates are not listed. If a delivery fails for good (for example a deleted webhook), the updates stay for the next day; if Google Chat keeps failing through all retries, that day's digest is lost. When many busy digest rules share the same hour, some may arrive an hour later.
Project admins
Project administrators can manage notifications for their own project without Jira admin rights: Space settings (or Project settings) → Apps → 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 about 30 seconds, then 2, 5 and 10 minutes, up to 5 attempts (8 for rate limits).
- Failed: the message could not be delivered, with the error shown. A wrong or deleted webhook is not retried.
- Not sent: the rule's JQL filter has an error: the JQL stopped working, for example because a field, label value or project it names was deleted. Edit the rule and fix the query. This is logged at most once an hour per rule.
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.
What Google's app does that Jaylert Chat doesn't (yet)
Jaylert Chat replaces the space notifications of Google's app. Check this list before you move; if your team uses one of these, keep Google's app for that part or tell us what you need. We add features based on what customers ask for.
| Feature in Google's app | Jaylert Chat today |
|---|---|
| Personal direct messages: issues you watch, reported, are assigned to or are mentioned in | Not available yet; planned for the next version. Until then, messages go to spaces set up by an admin. |
Create an issue from Chat (/jira_create) or show one (/jira_view) | Not available. Jaylert Chat only sends messages; it does not read Chat. |
| Previews of Jira links pasted in Chat | Not available. |
| @mentions of Google Chat users | Neither app does this. Jaylert Chat shows display names. |
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 | Space settings (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 | Up to 30 (fewer for very long texts), then "and N more issues" |
| Changes listed per issue in a digest | The last 8, then "+ N earlier updates" |
| Daily digest queue | 7 days (e.g. a long weekend) |
| Delivery attempts on temporary Google errors | 5 (after about 30 s, 2, 5 and 10 minutes); 8 when Google asks to slow down (rate limits). Waits are spread a little so many messages don't all retry at once. |
| 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 looks like https://chat.googleapis.com/v1/spaces/…/messages?key=…&token=…. |
| 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. |
| "Not sent: the rule's JQL filter has an error" | Something the query names no longer exists. Try the JQL in Jira's issue search, fix it there, then 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. Issues with a security level are skipped unless the rule allows them; issues the app can't see are never sent (see Issues with a security level). |
| "Not sent: the issue has a security level" | On purpose: see Issues with a security level. |
| "currentUser() cannot be used in a rule filter" | Rules run for everyone's changes. Name the user or group, e.g. assignee in membersOf("support-team"). |
| "Jira administrators only" on the admin page | Only Jira administrators can manage site rules. If you are one, reload the page and accept Allow access. |
| "Retrying" in the log | Google Chat limits busy spaces. Jaylert Chat retries on its own; no action needed. |
| "Could not load the rules" | Jira did not answer in time. Click Try again; your rules are not affected. |
| "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.