Chat Relay
JiraGoogle Chat™

Jira for Google Chat: “subscription fails” in a new space

A pattern reported on the Atlassian Community: the Jira app for Google Chat works in existing spaces, but in a new space /jira_connect succeeds and then /jira_settings shows an error as soon as you pick a project. Reinstalling doesn't help. Editing existing subscriptions can fail the same way.

What to try

  1. Make sure the Jira site is connected for your user in that space: run /jira_connect again from the new space, not a DM.
  2. Ask your Google Workspace admin whether the Jira app is allowed for everyone who is in the space (Admin console → Apps → Google Workspace Marketplace apps).
  3. Try a different browser or a private window. Browser extensions have broken the configuration card for some users.
  4. Contact Atlassian support. In a similar thread one user's setup started working after they contacted support.

We don't know the cause; it's inside the Jira app for Google Chat, which only Atlassian can fix.

Workaround: skip the subscription step

Notifications don't have to go through the Chat app. A space webhook receives messages without any /jira_settings step. You can post to it from a Jira Automation rule or from a webhook app. You can keep the Jira app in the space for creating issues.

Chat Relay posts Jira Cloud updates (new issues, status changes, assignments, public comments) to Google Chat spaces through a space webhook, with up to 10 spaces and per-space projects and events. No automation rules or JSON to maintain. Try the free beta while the Atlassian Marketplace listing is in review. See the setup guide.