Soon Coming to the Atlassian Marketplace · built on Forge
The Jira updates that matter, in Google Chat.
Jaylert Chat sends Jira events to your Google Chat spaces only when a rule says they matter: by project, JQL, event type and status transition. Every issue keeps its own thread.
Free for up to 10 users · from $0.60 per user per month, less for larger teams · Jira Cloud
Jira events 14
Support escalations
- Projects
- KAN
- JQL
- priority in (High, Highest)
- Events
- Status changed · Comment added
- Transition
- Any→Done
Google Chat 2 sent
Jaylert Chat 14:41 · thread KAN-128
KAN-128New comment
Fix is live. The customer confirmed payments go through again.
Jaylert Chat 14:32 · thread KAN-128
KAN-128Checkout fails for EU cards
Status In Review→Done
Open in JiraInstall count from the Atlassian Marketplace listing, September 2026.
Demo · 1:34
From rule to thread, in under two minutes.
A real Jira Cloud site and a real Google Chat space, recorded live. No mock-ups.
Built from real reviews
Seven complaints about Google's app. Seven answers.
We read the Marketplace reviews of Google Chat for Jira Cloud and built Jaylert Chat around what teams kept asking for.
It notifies us about everything.
There's no filter for status changes.
Every event starts a new thread.
It's one project or all of them.
Setup keeps failing on cookies and permissions.
Everyone has to configure it for themselves.
We can't change what the message shows.
Inside the app
Everything a Jira admin needs on one page.
A rule editor that speaks Jira
Projects, JQL, events and a from → to transition. JQL is checked when you save, so a typo never silently stops notifications.
Threads or a daily digest
Right away, threaded by issue, or one grouped card a day.
Cards your way
A delivery log you can read
30 days of results, metadata only.
| 14:41 | KAN-128 · comment | Sent |
| 14:32 | KAN-128 · status | Sent (2nd attempt) |
| 11:07 | OPS-44 · created | Retrying |
| 09:15 | test message | Failed: webhook deleted |
Retries when Google is busy
Rate limits and server errors are retried automatically. A deleted webhook is reported, not hammered.
Delivery
Right away, or once a day.
Each rule picks its pace. Escalations can land the minute they happen, while the rest of the project arrives as one tidy card every morning.
Right away
Threaded by issueOne message per event, in the issue's own thread. Best for escalations, incidents and approvals.
Daily digest
Your hour, your time zoneOne card a day, grouped by issue. Weekdays only if you like; weekend updates arrive on Monday.
Coming soon Next version of Jaylert Chat
Personal messages in Google Chat.
Spaces keep the team informed. Personal messages tell each person what needs them: a direct message from the Jaylert app in Google Chat when an issue is assigned to them, when they are mentioned, or when someone comments on their issue.
What people get
Only what concerns themOne message per event, with the reason on top. Never about their own changes, only about issues they can see in Jira, and never the text of a restricted comment.
How it will work
Each person decidesA Jira admin turns personal messages on for the site. Then each person connects their own Google Chat once, with a one-time code from Jira (Settings (⚙) → General settings → Apps → Jaylert Chat), and chooses what they get:
- Issues assigned to them
- Mentions in comments
- New comments on their issues
- Optional: status changes on issues they reported, updates on issues they watch
How data is handled: Privacy policy. This section changes to a setup guide when the version is released.
Security and data
Your issues stay in Atlassian's cloud.
Jaylert Chat is a Forge app: its code and storage run on Atlassian's infrastructure. It reads what a notification needs, sends it to the space you chose, and nothing else.
- Permissions
read:jira-workread:jira-userstorage:app. Read-only: Jaylert Chat cannot change your issues.- Outbound traffic
- One host:
chat.googleapis.com. - Webhook secrets
- Stored with Forge's encrypted secret storage. The admin page only ever shows the last characters.
- Stored data
- Rules and a 30-day delivery log with issue keys, event types and results. For daily digest rules, the issue key, summary and change wait in a queue until the digest is sent, at most 7 days; people appear there only as account IDs, never by name.
- Private comments
- Comments with restricted visibility and Jira Service Management internal notes are never sent.
- Developer access
- Our logs hold only technical details such as issue keys, rule names and error codes. We can't see issue content or your messages.
Setup
From install to first message in about two minutes.
Add a webhook
In the Google Chat space: Apps & integrations → Webhooks → Add webhook. Copy the URL.
Install Jaylert Chat
From the Atlassian Marketplace onto your Jira Cloud site. A Jira admin does this once.
Create a rule
Paste the webhook, choose projects, events and the fields for the card.
Send a test card
A sample card with your fields appears in the space. Real events follow.
Pricing
Per user, billed through Atlassian.
Every feature on every plan. Start with a 30-day free trial from the Marketplace.
Up to 10 users
Free
- All features, all 50 rules
- For small teams and pilots
11 users and more
from $0.25 per user / month
| First 100 users | $0.60 |
| Users 101 – 250 | $0.40 |
| Users 251 and up | $0.25 |
Estimate. Tiered like every Atlassian price list: each user is billed at the rate of the band they fall in, so 250 users cost 100 × $0.60 + 150 × $0.40 = $120. Annual plans cost 10× the monthly price. The Marketplace shows the final price.
FAQ
Questions teams ask first.
Do we need Google Workspace?
Yes. Incoming webhooks are a Google Chat feature for Google Workspace spaces. Your Workspace admin can allow or block them for the organization.
Does it work with Jira Service Management?
Yes, with any Jira Cloud project. Internal notes and comments with restricted visibility are never sent to Chat.
Jira Data Center or Server?
No. Jaylert Chat is built on Atlassian Forge, which runs on Jira Cloud only.
What doesn't Jaylert Chat do yet?
Jaylert Chat posts to Google Chat spaces. It does not yet send personal direct messages (for example "you were assigned"), @mention people in Chat, create or look up issues from Chat with commands, or show previews of Jira links pasted in Chat. Google's own app offers these. Personal direct messages are coming in the next version: see what they will do. If your team relies on one of the others, tell us: requests decide what we build next. Details
Can project admins set this up without a Jira admin?
Yes, once a Jira admin has installed Jaylert Chat. Project administrators then find it under Space settings (Project settings) → Apps and manage rules for their own project. Jira admins see every rule on the site.
Is there a daily summary instead of instant messages?
Yes. Any rule can send a daily digest at the hour and time zone you pick, optionally on weekdays only. Updates are grouped by issue in one card.
How many spaces can we connect?
Up to 50 rules per Jira site, each posting to its own space. Several rules can share a space; a matching event is still sent once.
What happens if Google Chat is down?
Jaylert Chat retries after about 30 seconds, 2, 5 and 10 minutes (longer when Google asks it to slow down). The delivery log shows every attempt and the final result.
Where is our data stored?
In Atlassian's Forge storage for your site, under Atlassian's data residency. Jaylert Chat has no database of its own.
We use Google's app today. How do we switch?
Create one rule per space, send a test card, then remove Google's app from the space. The migration guide walks through it.
Give your team a lookout.
Jaylert Chat is coming to the Atlassian Marketplace. The setup guide is ready now.