Use case: DevOps and IT operations updates

The problem

An operations team wants a narrow stream of Jira changes in the Chat space it already uses for service coordination. A broad stream of every issue change creates noise; project-wide visibility may also put more information in Chat than the team needs.

Starter configuration

1. Create an operations Chat space and a Chat Relay connection for it.
2. Select only the Jira project or JQL scope relevant to the team's handoffs.
3. Start with Blocked or High priority issues.
4. Use Key only for the first run. Preview matches and confirm the Chat audience.
5. Select immediate delivery for handoffs, or a digest for routine work.
6. Trigger a synthetic issue event and inspect the Chat message and delivery log.

Example message

OPS-42 · Status changed · Blocked · Open in Jira

Immediate changes to one issue use a stable Chat thread key. Quiet hours and hourly/daily digests can reduce interruptions for routine updates.

Safety and operational limits

This is a collaboration notification, not an alerting or paging system. It has no customer-facing uptime or delivery-time SLA, and a Google Chat outage or webhook limit can delay a message. Keep emergency escalation in the team's existing on-call service.

The app checks issue project scope and security before sends; it skips unknown or restricted issues. The Jira administrator must confirm the Google Chat membership and field visibility.