Send Jira issue updates and a daily digest to Google Chat spaces. Every update for an issue stays in one thread, so busy spaces stay readable.
Each rule can notify on any of these: issue created, status changed, issue resolved, assignee changed, priority changed, comment added. One update that changes several things at once (say, status and resolution) arrives as one card.
Limit a rule to some projects, or narrow it further with JQL. Only issues that match are sent. Examples:
priority in (Highest, High)labels = customer AND issuetype = Bug"Request Type" = "Get IT help"All updates for an issue are replies under its first card. You can turn this off per rule.
Choose priorities (for example Highest) that should mention everyone in the space. The mention appears as a short line above the card, so people get a notification.
Turn off Show comment text in Chat to post only that a comment was added, without its content. This is useful for internal notes in Jira Service Management.
The admin page lists the last 50 deliveries, each with its result. If Google Chat rejects a message, the log shows Google's reason. If Google is busy or rate-limits a space, ChatPulse waits and tries again once.
Create as many rules as you need (up to 100), for example one per team or project. Duplicate copies a rule so you only change what's different.
Turn on Daily digest in a rule to post a summary card every day at the hour you choose, in your time zone. The card lists up to 15 issues matching the digest JQL, each showing status, assignee and priority, with a link to see them all in Jira. Weekends can be skipped.
Good digest queries:
resolution = Unresolved ORDER BY priority DESC, updated ASCresolution = Unresolved AND updated <= -3d ORDER BY updated ASCassignee is EMPTY AND priority in (Highest, High) AND resolution = Unresolveddue <= endOfWeek() AND resolution = Unresolved ORDER BY due ASCUse Send digest now to preview it straight away.
| What the delivery log says | What it means and how to fix it |
|---|---|
| Google Chat returned 400: API key not valid | The webhook URL is incomplete or the webhook was deleted. Copy the link again from the space's Webhooks page and paste it into the rule. |
| Google Chat returned 403 | Webhooks are blocked for this space or by your Workspace admin, or the space is restricted. Ask your admin to allow incoming webhooks. |
| Google Chat returned 404 | The space no longer exists. Create a new webhook in an active space. |
| Google Chat returned 429 | Too many messages in a short time (Google allows about one per second per space). ChatPulse retries once. If it keeps happening, narrow the rule with JQL or split it across spaces. |
| JQL error: … | The rule's JQL filter is invalid. Test it in Jira's issue search, then paste the fixed query. |
| Nothing in the log | No rule matched. Check the rule is On, includes the project and event, and that its JQL matches the issue. |
No issue data is stored. ChatPulse runs entirely on Atlassian Forge and keeps only your rules, the last 50 delivery results and digest dates, all in Forge storage on Atlassian's infrastructure. Issue details go directly from Atlassian to the Google Chat webhooks you configure. They never pass through PuzariCloud servers. See the privacy policy.
Only Jira administrators. The settings page sits under Jira settings → Apps.
Yes. It works with any Jira Cloud project, including service projects, software and business projects.
Not yet. ChatPulse sends notifications from Jira to Chat. Each card has an Open button that takes you to the issue.
Pricing is on the Atlassian Marketplace listing and is billed by Atlassian. There's a free trial.
Email support@puzaricloud.in. Please include your Jira site address and, if possible, the line from the delivery log. We reply within one business day (Monday–Friday, India time).
Security issue? Email the same address with "Security" in the subject.