One thread per issue, only the changes that matter, and a setup that takes about two minutes. Runs on Atlassian Forge, with no servers of ours in between.
Free for teams of up to 10 users. Larger sites: see the Marketplace listing for pricing.
Every Jira event goes through the same five steps before anything reaches your team. Most events never become a message, and the ones that do are grouped.
Someone creates, edits or comments on an issue.
12 eventsIgnores Rank, sprint and board order changes.
4 ignoredBatches changes to the same issue into one.
8 changes, 3 issuesJQL, statuses and issue types decide what is sent.
3 matchEach batch lands as a card in the issue's thread in Google Chat.
3 cards12 events in,3 cards out
Illustrative numbers for a busy minute. Your rules decide what is sent.
A bulk edit, an import or a workflow clean-up can flood a chat space in seconds. When one person changes 10 or more issues in a minute, Maplesprint Notify sends a single summary instead. Administrators can adjust that threshold.
One message per issue, one after another, until the space is unreadable.
Ana Pérez updated 40 issues in 1 minute.
Maplesprint Notify
Bulk update in PROJ
40+ issues in PROJ were updated by Ana Pérez in the last minute. To avoid flooding this space, the individual notifications were combined into this summary.
View recent changesEveryone still knows it happened, and nobody has to scroll past it.
Built around the complaints people have about existing Jira and Google Chat integrations.
Choose what triggers a message: issue created, status changed, assignee changed, priority changed, resolved, or a new comment. Narrow it down with issue types, from and to statuses, or a JQL query. Status filters use status IDs, so renamed or translated workflows keep working.
Changes to the same issue within about 10 seconds arrive as a single card, and noisy fields such as board rank are ignored. If someone edits dozens of issues at once, your space gets one summary instead of a flood.
Every issue gets its own thread in the space. Choose when a new thread starts: every 24 hours, after 8 hours without changes, never, or no threads at all. A new thread notifies the space; replies stay quiet.
Cards show the key, summary, what changed (old and new value), assignee, priority, a comment excerpt and an Open in Jira button. Prefer less? Switch a rule to a compact one-line message.
Administrators connect Google Chat spaces once. Project administrators then add rules from ready-made templates, check their JQL, and press Send test. A delivery log shows the last 50 messages per space.
No servers of ours: the app runs on Atlassian Forge and talks only to Google Chat. Webhook URLs are stored encrypted. Issues with a security level are skipped unless an administrator turns them on.
Each rule has a Notify everyone (@all) switch, off by default. Google Chat webhooks cannot mention individual people, so names such as the assignee appear in bold.
Check that you copied the whole URL, including key and token. If it still fails, your Google Workspace administrator may have blocked incoming webhooks (Google Admin console, Apps, Google Workspace, Google Chat). Ask them to allow webhooks for the space.
In Google Chat, replies inside a thread are quiet unless you follow the thread, and they appear collapsed as "N replies". The first message of a new thread notifies the space. Use a shorter thread setting on important rules, or turn on Notify everyone (@all) for them.
Usually within 10 to 30 seconds. Jira can occasionally take up to a few minutes to deliver an event to any app, and Google Chat allows about one message per second per space, so busy periods are retried automatically.
Open Jira settings, Apps, Maplesprint Notify, Delivery log, and pick the space. Each delivery shows as sent, skipped (with the reason) or error. Common reasons: the issue has a security level, the JQL does not match, or the rule is paused.
They are skipped by default, because the app can read more issues than most people and a Google Chat space could expose issues some of its members cannot open in Jira. A Jira administrator can turn this on in the app settings.
Direct messages to individual people, mentions of individual people and actions from Google Chat need a Google Chat app, and are planned for a later edition. Daily digests and quiet hours are also planned.
When a rule matches, the app sends a message to the Google Chat space you chose: issue key, summary, issue type, status, priority, assignee and actor names, the changed values, a comment excerpt of up to 500 characters and a link to the issue. Nothing goes anywhere else, and we never receive your data. Read the privacy policy for the full list of what is stored.
Questions, bugs or ideas? Write to support@maplesprint.com. We aim to reply within two business days. See the terms and support policy.
Tell us how your team uses Jira and Google Chat and we will invite you to the early access.
