Use case: Jira administrator routing updates to team spaces

The problem

A Jira administrator has several teams sharing Jira, but not every project change belongs in the same Google Chat space. Generic notifications are noisy, while a custom Automation rule for every destination takes ongoing setup and diagnosis.

Starter configuration

1. Create one Chat Relay connection for a team space.
2. Select a single Jira project or a narrow JQL scope.
3. Start with the Blocked or New Highest / High priority issue preset.
4. Choose Key only until the space audience and field visibility are confirmed.
5. Preview current matching issues, send a test, save, and trigger one synthetic issue event.
6. Review the delivery log after the first real event.

Presets create a starter event rule; review all settings before widening its scope. Connection health, recent delivery outcomes, queue state, and retries are visible in Jira.

Example message

CP1-207 · New high-priority issue · Open in Jira

The example is synthetic. A key-only card avoids adding the issue title or selected fields to the Chat message.

What this does and does not solve

Chat Relay routes selected Jira issue events into Google Chat. It groups immediate updates for one issue in a stable thread, supports quiet hours and hourly/daily digests, and shows delivery status.

The app is not a paging service and does not promise a delivery SLA. Restricted or unverified issues are skipped; the admin remains responsible for Google Chat space membership.

First success signal

A real matching event appears in both Google Chat and the delivery log. A successful test message alone is not activation.