Overview
This guide outlines the key differences between the Advanced Google Chat for Jira Data Center and Advanced Google Chat for Jira Cloud versions by Move Work Forward.
Both versions provide Jira notifications within Google Chat spaces, however some functionality differs due to platform capabilities and Atlassian Cloud limitations.
Notification Rule Types
|
FEATURE |
DATA CENTER |
CLOUD |
|---|---|---|
|
Global Notification Rules |
Supported |
Supported |
|
Space-Level Notification Rules |
Supported |
Supported |
Supported Notification Events
|
NOTIFICATION EVENT |
DATA CENTER |
CLOUD |
|---|---|---|
|
Issue created |
Supported |
Supported |
|
Issue updated |
Supported |
Supported |
|
Issue commented |
Supported |
Supported |
|
Comment edited |
Supported |
Supported |
|
Comment deleted |
Supported |
Supported |
|
Issue assigned |
Supported |
Supported |
|
Issue deleted |
Supported |
Supported |
|
Issue moved |
Supported |
Supported |
|
Work logged |
Supported |
Supported |
|
Issue link deleted |
Supported |
Supported |
|
Issue linked / Issue link created |
Supported |
Supported |
|
Issue resolved |
Supported |
Not Supported |
|
Generic (includes status changes) |
Supported |
Not Supported |
|
Attachment added |
Supported |
Not Supported |
|
Attachment removed |
Supported |
Not Supported |
|
Issue closed |
Supported |
Not Supported |
|
Issue reopened |
Supported |
Not Supported |
|
Work started |
Supported |
Not Supported |
|
Work stopped |
Supported |
Not Supported |
|
Issue transition |
Not Supported |
Supported |
|
Version released |
Not Supported |
Supported |
|
Sprint created |
Not Supported |
Supported |
|
Sprint started |
Not Supported |
Supported |
|
Sprint closed |
Not Supported |
Supported |
Space/project Configuration Differences
|
FEATURE |
DATA CENTER |
CLOUD |
|---|---|---|
|
Exclude individual spaces/projects directly |
Supported |
Not Supported |
|
Include specific spaces/projects |
Supported |
Supported |
Filtering Options
|
FILTER |
DATA CENTER |
CLOUD |
NOTES |
|---|---|---|---|
|
Issue status filter |
Supported |
Not Supported |
Restrict a rule to specific issue statuses. No Cloud equivalent. |
|
Notify only on specific field changes |
Supported |
Not Supported |
Data Center can restrict a rule to only fire when particular fields change. No Cloud equivalent. |
|
JSM private comment awareness |
Not Supported |
Supported |
Cloud can recognise and skip Jira Service Management private (internal) comments. Data Center has no Jira Service Management integration at all. |
|
Issue type, priority, component, and label filters |
Supported |
Supported |
Available on both, with equivalent (though not identically structured) matching options. |
Notification Card Configuration
|
CONFIGURATION OPTION |
DATA CENTER |
CLOUD |
|---|---|---|
|
Do not send message details |
Supported |
Supported |
|
Use threads |
Supported |
Supported |
|
Show Jira issue details by default |
Not Supported |
Supported |
Key Behaviour Differences
|
AREA |
DATA CENTER |
CLOUD |
|---|---|---|
|
Status change handling |
Generic event |
Dedicated Issue transition event |
|
Sprint notifications |
Not Supported |
Supported |
|
Version release notifications |
Not Supported |
Supported |
|
Project exclusion support |
Direct exclusion available |
Requires manual inclusion approach |
Migration Considerations
Notification rules migrate automatically when you use the Jira Cloud Migration Assistant, including their project, issue type, and most other filters, alongside the rest of your Jira data. A small number of Data Center-only features shown in the tables above (excluded-project lists, status filters, the field-change filter, and five Data Center-specific events) have no direct Cloud equivalent - any rule using one of these is imported disabled for review rather than silently narrowed or widened.
If you're not using the Migration Assistant, notification rules can still be recreated manually.
See the full migration guide for the complete walkthrough, including exactly what carries over automatically and what needs a manual check afterwards.
It is recommended to validate all critical notification workflows after migration.
Support
If you have any questions about feature parity, migration planning, or configuration differences, please contact the Move Work Forward Support Team.
Updated: September, 2026