Comments tab
In this tab, it is possible to select how comments are synchronised between issues.
This tab is not available when the target is a remote Jira instance.
![capture-comments.png](../__attachments/10967548354/capture-comments.png?inst-v=9fdb14ed-4bc9-4150-9682-af9fdd6c0846)
The comments synchronisation options are listed in several subsections, which availability depends on your current configuration.
Comments synchronisation
Enable : When this option is set to "Yes", every new comment posted in the source issue will be also created on the issue targeted by the synchronisation. Otherwise, comments won't be synchronised.
Restrictions : This option allows you to decide which comments should be synchronised to the target issue, depending on their visibility in the source issue.
Synchronise all comments
Synchronise public comments : only public comments (in JSM) or comments "Viewable by All Users" (in Jira Software) will be synchronised to the target issue.
Synchronise restricted comments : only internal comments (in JSM) or comments "restricted" to a given group of users (in Jira Software) will be synchronised to the target issue.
Exclude users : The comments made by these users will not be synchronised to the target issue.
Exclude groups : The comments made by users belonging to these groups will not be synchronised to the target issue.
Edits and deletions
Sync edits : When this options is enabled, edits made to the original comment are echoed to the synchronised comment.
Sync deletions : When this options is enabled, when the original comment is deleted, the content of the synchronised comment is replaced by "Message deleted from the original issue."
Author of synchronised comments
Author : This option allows you to decide which Jira user will appear as the author of the comments synchronised to the target issue. This option is only displayed when a Synchronisation Author has been set in the Author tab.
Post as original comment's author
Post as Synchronisation Author : the author of the synchronised comments will be the Synchronisation Author
Post as Synchronisation Author (only for comments) : this option should be used if you want the Synchronisation Author to be used only to synchronise comments, and not as the author of other synchronised updates (such as Fields updates).
Synchronisation to JSM
This subsection is only visible if Jira Service Management is installed on the current Jira instance.
Visibility in JSM : This option allows you to set the visibility ("internal" or "public") of the comments that will be synchronised to Jira Service Management projects by Copy & Sync. When configured, it will allow you to bypass the common JSM limitation which prevents comments synchronised from a standard JIRA project (Core or Software) to be visible to customers if the original author cannot post public comments in JSM.
Always private : comments posted in the target issue in JIRA Service Management project will always be internal.
Always public : comments posted in the target issue in JIRA Service Management project will always be public.
Keep original comment visibility : comments posted in the target issue in JIRA Service Management will keep the original chosen visiblity ("internal" or "public").
Use permission level of the original comment's author : the visibility of the comment posted in the target issue depends on the original author's permission.
The options availability here depends on whether a Synchronisation Author has been set as the author of synchronised comments, and on whether this user has an active JSD license or not.
Always private | Always public | Keep original comment visibility | Use permission level of the original comment's author | |
---|---|---|---|---|
Sync Author with JSM license | AVAILABLE | AVAILABLE | AVAILABLE | X |
Sync Author without JSM license | AVAILABLE | X | X | X |
No Sync Author | AVAILABLE | X | X | AVAILABLE |
Note: To be able to post comments, the Synchronisation Author should also have both "Add comments" and "Browse project" permissions on the JSM project.
Display comments origin
Display : When this option is enabled, a flag will be put in synchronised comments to indicate that they originate from another issue. This header / footer will display information on the original issue :
![footer-in-message.png](../__attachments/10967548354/footer-in-message.png?inst-v=9fdb14ed-4bc9-4150-9682-af9fdd6c0846)
Location : Here you can decide if the flag will be displayed above or below the original comment.
Custom label : You can customized the message to display in the header or footer, and add several information from the original comment that you may want to detail in the synchronised comment.
By default, we use the following message : "This $visibility message was originally posted by $author in issue $issue.key".
In this message, the variables are information from the original comment :
"$visibility" is the original comment visibility, it indicates if the original comment was public or restricted/internal.
"$author" is the username of original comment author, this option can be particularly useful when a Synchronisation Author is used to post comments.
"$issue.key" adds a link to the original issue.
More information from the source can be retrieved by using different velocity values starting with "$issue." detailed in the velocity documentation.