How to fix the Jira app in Google Chat when it stops working

Google Chat has a Jira app that posts issue updates to spaces and direct messages. When it breaks, the symptoms are usually the same: the Configure link shows an error, settings will not save, or notifications quietly stop. Here are the fixes that Jira admins report working, in the order worth trying, and what to use if you want a setup that does not depend on a bot login.

How the Jira app in Chat is set up

There are two halves, and both must be in place:

Notifications are configured per space. Adding the app to one space does not subscribe any other space.

Fix 1: open the configuration link in Chrome or Edge

The most common report on the Atlassian Community is an error page right after clicking Configure or Connect. Several admins fixed it by opening the same link in Google Chrome or Microsoft Edge instead of Brave or Firefox. Privacy browsers and strict tracking protection can block the sign in step between Google and Atlassian.

Fix 2: allow cookies for your Jira site

The connection flow needs cookies for your atlassian.net site. If you block third party cookies, add an exception for your Jira site and for Google Chat, then retry the connection.

Fix 3: reopen and save the settings

In the space, run the Jira app's settings command (listed in Google's help as /jira_setting), open the notification settings, and save them again without changes. One admin reported this restored a connection that had been broken for months. You can also run /jira_subscriptions to check which projects the space is actually subscribed to.

Fix 4: reinstall the Jira plugin

  1. In Jira, go to Apps, then Manage your apps.
  2. Uninstall the Google Chat plugin for Jira, then install it again from the Atlassian Marketplace.
  3. In Chat, run /jira_disconnect in the space, then /jira_connect, and set up the subscription again.

Admins in the same Community thread say reinstalling fixed it, though for some the problem came back later. Write down your project subscriptions first, because you will need to recreate them.

Fix 5: check it is not a permissions or plan issue

Plan ahead: Connect end of support in January 2027

Atlassian is retiring Connect, its older framework for Jira Cloud apps. Connect end of support begins on January 31, 2027. After that, Atlassian says it will only fix critical security issues, and Connect apps that have not moved to Forge may break without notice. If your Jira to Google Chat integration is important, ask its publisher whether it runs on Forge or has a published Forge migration plan. Apps built on Forge are not affected by this deadline.

Alternative 1: Jira Automation and a Google Chat webhook (free, within plan limits)

A webhook skips the bot login entirely. In the Chat space, open the space name, then Apps & integrations, then Webhooks, and add one. In Jira, create an Automation rule with a trigger such as Issue created and a Send web request action that POSTs a small JSON message to the webhook URL. Step by step instructions are in our Jira to Google Chat guide. Webhooks need Google Workspace Business or Enterprise with webhooks allowed by your admin, every message counts toward your Automation usage, and you maintain the message format yourself.

Alternative 2: a Forge app that uses webhooks

Threadline for Jira posts filtered Jira and Jira Service Management notifications to Google Chat through incoming webhooks, so there is no bot to authorize and no browser sign in flow to break. You paste a webhook URL, send a test message, and route by project, event, issue type, priority, status, labels, assignee or JQL. It keeps one thread per issue, batches bursts, sends daily digests, respects quiet hours, never posts internal JSM comments, and shows every delivery and filter decision in a log. It runs on Atlassian Forge, is free for up to 10 users, then $0.80 per user per month through Atlassian, and is pending Atlassian Marketplace review.

Frequently asked questions

Why does the Jira app in Google Chat show an error when I click Configure?

Usually the browser is blocking the sign in step. Open the link in Chrome or Edge, allow cookies for your Jira site, and retry. If it still fails, reinstall the Chat plugin in Jira from Apps, Manage your apps.

Why did my Jira notifications in Google Chat stop?

The connection may have expired or the space lost its subscription. Run the settings command in the space, check subscriptions with /jira_subscriptions, and save the settings again. Reconnect with /jira_disconnect and /jira_connect if needed.

Do I need a Jira admin to fix it?

Often yes. Installing or reinstalling the Chat plugin in Jira needs a Jira admin, and allowing Chat apps or incoming webhooks needs a Google Workspace admin.

What happens to Connect apps after January 31, 2027?

Atlassian ends support for Connect on that date and will only address critical security issues. Connect apps that have not adopted Forge may stop working without notice, so ask your app publisher about their Forge plan.

Is there a way to send Jira updates to Google Chat without the Jira app?

Yes. Use a Google Chat incoming webhook with a Jira Automation rule, or a Forge app such as Threadline for Jira that delivers through webhooks with filters, threads and digests.

Related guides