ChatBridge · v0.1

Your Jira, in your Google Chat.

ChatBridge posts the issue updates each team actually cares about to the right Chat space, and keeps every issue in one tidy thread.

Google Chat · #payments
JiraApp9:41
PAY-142: Status changed: To Do → In Progress by Ana Ruiz
PAY-142 · Checkout fails on SafariPayments · Bug
Event
To Do → In Progress
Priority
High
Status
In Progress
Assignee
Ana Ruiz
Open in Jira
↳ 3 replies · Leo commented “Fixed in build 2.4.1”

How it works

Four steps. No Google Cloud project.

No service accounts, no OAuth screens, no third-party cookies. If you can paste a URL, you can set this up.

01InstallA Jira admin adds ChatBridge from the Atlassian Marketplace.
02Copy a webhookIn the Chat space: Apps & integrations → Webhooks.
03Add a rulePick events and, if you like, a JQL filter.
04Send testSee it land in your space. That's it.

Spec sheet

Built so you never think about it again.

Integrations fail quietly: a rate limit here, a duplicate there, a webhook that stopped working months ago. ChatBridge is designed around those failures.

Events
Issue created · status changed · assignee changed · comment added (first 300 characters)
Filters
Any JQL Jira understands, one rule per space, up to 50 rules
Threads
Every update about an issue goes into the same thread
Busy spaces
Automatic retries with backoff when Google Chat rate-limits a space
Duplicates
The same change within 30 seconds is posted once
Restricted comments
Comments limited to a role or group are never posted with their text. Service desk internal notes are clearly labelled.
Secrets
Webhook URLs encrypted in Atlassian Forge storage and never shown again
Data to us
None. Runs on Atlassian Forge; it only talks to chat.googleapis.com

Switching from another integration?

Atlassian ends support for its older Connect app framework on January 31, 2027. Many older Jira integrations are built on it, including some for Google Chat. After that date they may stop getting fixes or stop working reliably. ChatBridge is built on Forge, Atlassian's current platform. Read the 4-step migration checklist →

Questions

The honest answers.

What data leaves Jira?

Only the message posted to the space you chose: issue key, summary, project, type, status, assignee, priority, a 300-character comment preview and a link. Nothing is sent to us. See the privacy policy.

Can people in a space see issues they can't open in Jira?

Yes. Anyone in the space sees what's posted there. Keep confidential projects out with JQL, and post sensitive work only to spaces with the right members.

Do you send direct messages to individuals?

Not yet. Personal notifications ("ping me when I'm assigned") are the next big feature on the roadmap.

Do I need my Google Workspace admin?

Only if your organization has turned off incoming webhooks for Chat. They're on by default.

What does it cost?

Free during early access. Pricing will be on the Atlassian Marketplace listing well before any charge applies.

Changelog

What's new.

  1. v0.1.0 · November 2026
    First release: rules with JQL, four event types, threads per issue, retries, duplicate protection and a "Send test" button.
  2. Next
    Personal notifications, per-rule message fields, Confluence page updates.