Guides for Jira teams

Guide · Connect end of support

Google Chat for Jira Cloud and the end of Connect: keep your Jira notifications

If your team gets Jira updates in Google Chat through Google's own app, here is what Atlassian's move away from Connect means for it, what to write down before anything changes, and how to move the notifications without a gap.

What is changing

  • Connect end of support is 31 January 2027. After that date Atlassian no longer supports Connect apps, and they may stop working as the platform changes.
  • Connect apps can no longer ship updates through the Marketplace since spring 2026.
  • Jira has started telling admins, and then users, when an installed app "might stop working soon".

Apps built on Forge, Atlassian's current platform, are not affected.

Is your Google Chat app affected?

On the Atlassian Marketplace, Google Chat for Jira Cloud by Google LLC is listed as a Connect app: its latest cloud version is 1.1.0-AC (the -AC ending marks Connect), released on 11 November 2021, as of November 2026. It has close to 11,000 installs and an average rating of 2.3 from 110 reviews. Two ways to check your own site:

  • In Jira, open Apps → Manage your apps and look for the "might stop working soon" notice next to Google Chat for Jira Cloud.
  • Ask Google Workspace support whether a Forge version is planned. If one is coming, the simplest path may be to wait for it.

Nothing to export, but something to write down

Notifications hold no data you need to keep: the messages already in your spaces stay there. What you lose with the app is the setup: which projects post to which space, and which events. Write it down before you change anything.

Write down your current setup

  • Every Google Chat space that receives Jira updates, and who relies on it (a team, support, release managers).
  • For each space: which projects or issues, and which events (new issues, status changes, comments, assignments).
  • Anything people complain about today: too many messages, missing updates, private comments showing up. A switch is the time to fix it.

A calm way to switch

  1. Install the replacement next to the old app

    Both can run side by side. For a day, a space may get each update twice: that is the overlap, not a fault.

  2. Connect one space first

    Recreate its rules, then change a test issue and check the message arrives where and how you expect.

  3. Move the other spaces

    One by one, from your list.

  4. Remove the old app

    Uninstall Google Chat for Jira Cloud in Jira, and remove its bot from the spaces.

Choosing a replacement

  • Built on Forge (look for "Runs on Atlassian" or ask the vendor), so you don't face the same move again.
  • Filters per space, for example by JQL, so each team gets only its own issues.
  • Keeps restricted content out: comments limited to a role or group, internal notes in Jira Service Management, issues with a security level.
  • Groups updates, so a busy issue doesn't flood the space.

Several Forge apps send Jira updates to Google Chat, among them Advanced Google Chat for Jira by Move Work Forward and Google Chat for Jira by Canary Apps. Chatline – Google Chat notifications for Jira (made by us, YTI Digital) is one more: it posts through a space's incoming webhook, so there is no bot to add, gives each space its own JQL filter, keeps every update of an issue in one thread, adds sprint and release cards and a daily digest, and never posts restricted comments or internal notes. It is free for up to 10 users. Its getting started page takes about five minutes, and we help at support@yti.digital.