Overview

Jira updates in Google Chat

Chatline posts Jira changes to the Google Chat spaces where your teams already talk. Each space gets only the issues and the kinds of changes it asked for.

What it does

  • New issues, status changes, assignee and priority changes, comments and other field edits, as a card with an Open in Jira button.
  • One space, one filter. Connect as many spaces as you need, each with its own JQL: the support team gets project = HELP, the release channel gets fixVersion = 2.0.
  • One thread per issue, no spam. Every update of an issue lands in the same Google Chat thread, and quick edits are bundled into one message.
  • Sprints and releases. A card when a sprint starts or ends and when a version is released, each with its issues.
  • Daily digest. One summary a day per space: what changed, what is overdue, what is due soon.
  • Your own messages. A Send Google Chat message action for Jira Automation rules, with smart values.
  • Safe by default. Comments restricted to a role or group, internal notes in Jira Service Management and issues with a security level are never posted.
  • You can see it working. A test button, and per space: how many messages were sent and the last error in plain words.

How it works

A Google Chat space gets an incoming webhook (a secret URL). A Jira administrator pastes it into Chatline and chooses what the space should receive. When an issue changes, Chatline checks each connected space and posts a message to the spaces that want it. Messages go one way: from Jira to Google Chat.

What you need

Jira Cloud, and a Google Workspace account (Business or Enterprise) that may add incoming webhooks to spaces. If Add webhooks is missing in a space, your Google Workspace administrator turned webhooks off.

Start here