What is posted
| Jira event | Message in Google Chat |
|---|---|
| Issue created | Issue key and summary as a link, type, priority, assignee and who created it |
| Status changed | Old and new status, and who moved it |
| Assignee changed | New assignee and who assigned it |
| Comment added | Author and the first 600 characters of the comment |
All messages about one issue land in one Google Chat thread, so a space stays readable even with many open issues. Threads can be switched off per connection.
In Jira Service Management, internal notes are left out unless a connection is set to include them, so agent-only notes do not reach a space shared with others.
Setup
- Install Ulte Chat for Jira from the Atlassian Marketplace.
- In Google Chat open the space, click the space name, then Apps & integrations → Webhooks → Add webhook. Copy the URL.
- In Jira open Settings → Apps → Google Chat notifications and click Add connection.
- Paste the URL, choose projects and events, click Send test message, then Save.
Incoming webhooks in Google Chat are available on Google Workspace Business and Enterprise editions. A Workspace administrator can turn them on or off for the organisation.
Connections
- Each connection links one Google Chat space to a set of Jira projects, or to all projects.
- Each connection has its own events, thread setting and internal note setting.
- Several connections can post the same project to different spaces, for example support and engineering.
- A delivery log on the settings page shows the last 30 messages with the result from Google Chat.
- Google Chat accepts one message per second per space. Messages over that limit are retried automatically.
Data and privacy
Ulte Chat for Jira runs entirely on Atlassian Forge, inside Atlassian's cloud. Jira data is never sent to Ulte servers. Settings, including webhook URLs, are kept in Forge storage on the customer's Jira site; webhook URLs are stored as secrets and shown masked after saving.
The only external service the app contacts is chat.googleapis.com, to post messages to the spaces an administrator connected. Messages contain the issue key, summary, link, type, priority, status, display names of the people involved and comment text. Details in the privacy policy.
Pricing
Billed by Atlassian through the Atlassian Marketplace, per Jira user, monthly or yearly, with a free trial. Current prices are on the Marketplace listing. Use is governed by the terms for Jira apps.
Support
Email info@ulte.net with the Jira site address and, if a message did not arrive, the result shown in the delivery log. Replies within one business day (Monday to Friday, Central European Time). Product updates are listed in the changelog.
Questions
Does it work with Jira Service Management?
Yes. Requests behave like issues; customer comments are posted and internal notes are optional.
Can messages go to direct messages instead of a space?
Not in this version. Google Chat webhooks post to spaces. Personal notifications are on the roadmap.
Why is a webhook used instead of a Google sign-in?
A webhook needs no Google account connection, no OAuth consent and no third-party cookies in the browser, which are the usual reasons Jira and Google Chat integrations fail to set up. It only allows posting to the one space it belongs to.
What happens if the webhook is deleted in Google Chat?
Deliveries to that space fail with an error in the delivery log. Adding a new webhook and pasting its URL into the connection fixes it.
Is it made by Google or Atlassian?
No. Ulte Chat for Jira is an independent app by Ulte, not affiliated with or endorsed by Google or Atlassian.