The challenge of synchronizing comments across linked Jira Service Management (JSM) issues—such as syncing from a problem ticket to multiple incident tickets—is significant. Often, the automation itself is straightforward, but the critical question remains: should every comment be visible to customers?
The Risks of Static Settings
Standard Jira automation often relies on static settings for "share with customers." Enabling this option forces all comments to be public, while disabling it keeps them all internal. Neither approach works for real-world support desks, which require a mix of internal technical discussions and public-facing updates. Manual intervention to copy and paste these comments creates operational bottlenecks and introduces the risk of accidentally exposing sensitive internal engineering details to customers.
Implementing Dynamic Logic with Smart Values
To solve this, we can leverage Jira automation's dynamic decision-making capabilities using the {{comment.internal}} smart value within conditional if-else blocks:
- If the comment is internal: When {{comment.internal}} returns true, use an "Add comment" action restricted to internal roles (e.g., administrators or the support team).
- Else (Public comment): When {{comment.internal}} returns false, use an "Add comment" action that leaves visibility unaltered, ensuring the update is shared with the customer.
This automated segregation ensures that internal engineering data is kept secure while customer-facing updates happen instantly.
Best Practices for Implementation
- Test Thoroughly: Always deploy and test your automation rules in a non-production project first.
- Monitor Audit Logs: Use the audit logs to verify that your if-else branches are executing as expected.
- Maintain Separation: Ensure internal comments remain focused on technical details while customer-facing notes are clear and professional.
- Regular Reviews: Periodically review your automation rules to align with evolving support processes and avoid redundancy.
By utilizing smart values and conditional logic, support teams can drastically reduce manual effort, improve efficiency, and mitigate the risk of data exposure.
