First Jira-to-Chat delivery in five minutes
This quick path starts after the Jira app is installed and a Google Chat incoming-webhook URL has been copied from the target test space. Creating a Workspace account, enabling webhooks, Marketplace approval, and installation permissions can add time and are not part of this setup timer.
Before you start
- Jira administrator access, or project administrator access for the selected project.
- A Google Workspace test space with incoming webhooks enabled.
- The space webhook URL copied securely. Treat it as a password and never paste it into a support ticket.
- A small synthetic Jira project and one issue that can match the rule.
Timed path
| Target time | Action |
|---|---|
| 0:00 | Open Chat Relay for Jira and choose Add connection. |
| 0:30 | Name the connection and paste the prepared webhook URL. |
| 1:00 | Select one project and a starter preset, such as New Highest / High priority issue. |
| 2:00 | Choose Key only or selected fields. Preview matching issues and confirm the Chat space audience may see them. |
| 3:00 | Send the connection test, confirm it appears in the test space, then save. |
| 4:00 | Create or transition one synthetic matching issue. |
| 5:00 | Confirm the real issue event appears in the delivery log and in Google Chat. |
A test message proves that the webhook works; it does not prove the Jira event rule is active. Trigger a real matching issue event before you call setup complete.
Measured DEV result
On 2026-10-16, the D4 development run measured 67.056 seconds from opening the preset wizard to first successful issue-event delivery. The preset was New Highest / High priority issue, scoped to the synthetic CP1 project, with Key only visibility. The delivery log recorded HTTP 200. See the original captures under assets/verified-dev-2026-10-16/.
This measurement does not include Marketplace installation, Google Workspace setup, webhook creation, admin approval, or any production action. The under-five-minute claim applies to configuring an already-installed app with the webhook ready. Owner must time the full public onboarding path in a clean isolated profile before advertising the broader claim.
If the message does not arrive
- Confirm the connection test succeeds and the webhook is still valid.
- Check that the Jira issue is in the selected project and matches the preset.
- Open Delivery log and use the visible HTTP result and reason.
- Confirm the space membership is appropriate for the Jira fields being sent.
- Do not send the webhook URL, issue contents, or access tokens to support.
For every send, the app checks current project scope and issue-security level. It skips delivery when it cannot prove that the issue is in scope and unrestricted. Jira permissions and Google Chat membership remain separate; the Jira administrator is responsible for the Chat audience.