Why JSM Comments Sync With the Wrong Visibility
When Jira Service Management comments sync with the wrong visibility, the root cause is rarely obvious because several different mechanisms can produce the same broken result.
Four distinct failure points commonly cause this:
- Author-based mapping – The sync tool uses the original author’s permissions to set visibility, overriding expected public or internal outcomes.
- Missing outgoing filters – Internal notes leave the source project because no filter blocks them before transmission.
- Undefined incoming classification – The target project receives comments without explicit visibility rules, so JSM applies an incorrect default.
- Proxy user permissions – The sync user lacks the required project role, causing comments to land incorrectly or disappear entirely.
The internal flag and project role restrictions are two unrelated mechanisms that both control comment visibility but require completely different handling in scripts and permission schemes. The visibility setting applied to synced comments can also be controlled by choosing to keep original comment visibility, ensuring the internal or public status from the source issue is preserved in the target JSM project. Integrated systems also reduce downtime and streamline workflows, contributing to reduced downtime.
How Public and Internal Comments Work in JSM
Before any comment sync between projects can be configured correctly, it helps to understand how Jira Service Management classifies comments at the source.
JSM uses two comment types:
JSM classifies every comment as either a public reply or an internal note — and the distinction matters.
- Public comments – Created via “Reply to customer,” visible on the customer portal and in email notifications.
- Internal notes – Created via “Add internal note,” visible only to team members in the Jira issue view.
JSM treats comments as internal by default unless an agent explicitly selects the customer-facing option.
Customer replies processed through the Service Management mail handler are classified as public.
Replies handled by the standard Jira mail handler may default to internal. An agent can also change internal to external by editing an existing comment directly in Jira.
Workflow step properties in the Service Management workflow can also affect comment visibility, where a misconfigured jira.permission.edit.user.1 property key may cause comments added during a resolve transition to be set as internal regardless of agent intent.
When integrating multiple projects, consider using an API gateway to enforce consistent comment visibility controls across systems.
What Causes Comment Visibility Breaks Between Linked Projects
Comment visibility breaks between linked Jira Service Management projects rarely stem from a single cause, but they share a common pattern: a gap between how the source project classifies a comment and how the destination project receives or displays it.
Several distinct failure points produce this gap:
- The proxy user lacks the project role needed to read restricted comments
- Outgoing sync rules omit filters that block internal notes from leaving
- Incoming rules fail to apply the correct public or internal classification
- Platform module state hides visibility controls entirely
- Separate browse or comment permissions make comments appear missing when they exist
Administrators encountering this behavior can verify whether the root cause is a global setting by navigating to Jira Settings, then System, and reviewing the General Configuration for Comment visibility to confirm it is set to Groups & Project Roles or Project Roles only. In Jira Service Management Data Center, the comment visibility dropdown displaying alongside Share with customer and Comment internally buttons is expected behavior tied to backward compatibility maintained for comments created before agent-based licensing was introduced.
Consider also evaluating your integration framework to ensure processes and roles align with your business objectives and support consistent comment visibility.
Map Comment Visibility Correctly in Your Sync Rules
Visibility mapping is one of the most important settings to configure correctly when syncing comments between Jira Service Management projects. A default “copy comments” setting rarely handles visibility differences between source and target projects.
Visibility mapping is critical—default “copy comments” settings rarely account for the differences between source and target projects.
Instead, sync rules need a dedicated mapping step that explicitly defines how internal, public, and restricted comments transfer. Some platforms offer preset options:
- Always private
- Always public
- Keep original comment visibility
- Use permission level of the original comment’s author
These presets let one sync rule adapt to different JSM project policies without custom scripting, eliminating ambiguity around where comment visibility responsibility sits. This functionality is supported across a wide range of releases, including Zendesk Version 5.0.0 through the most recent versions.
By default, internal comments sync internally while public comments are ignored, meaning explicit configuration is required to change how each comment type is handled across projects. Many organizations also see measurable operational improvements when they standardize comment visibility mappings to reduce miscommunication and security incidents operational cost reductions.
Confirm Public Comments Stay Public After Configuration
After configuring visibility mapping rules, teams should verify that public comments actually arrive as public in the target project—not just assume the settings worked.
Submit a test comment through the source project using the “Reply to customer” path, then check how it appears in the destination project.
Confirm the following:
- The comment displays as public, not an internal note
- The sync user holds JSM agent permissions in the target project
- Elements Copy & Sync shows “Always public” or “Keep original comment visibility” selected
If the comment lands as internal, revisit the target-side visibility rule—misconfiguration typically happens there, not at the source. Special keywords can trigger a comment to switch from internal to public depending on how the synchronization comments section is configured.
In Jira automation, using `{{comment.body}}` instead of `{{issue.comments.last.body}}` ensures the rule evaluates only the newly added comment, preventing earlier comments from unintentionally affecting the visibility of all future comments.
Also verify that your integration uses proper versioning to avoid unexpected behavior when projects or apps are updated.
