Jira work item "Internal note" being synced for some issues despite them being excluded in config

[Martin_Bosano]

Hi,

For some reason Internal Notes added to some work items (at least one) added in our cloud Jira synced to customer DC instance despite it being excluded from sync.

Outgoing sync from our instance is like
–
replica.key = issue.key
replica.type = issue.type
replica.assignee = issue.assignee
replica.reporter = issue.reporter
replica.summary = issue.summary
replica.description = issue.description
replica.labels = issue.labels
replica.comments = issue.comments.findAll{!it.internal}
replica.resolution = issue.resolution
replica.status = issue.status
replica.parentId = issue.parentId
replica.priority = issue.priority
replica.attachments = issue.attachments
replica.project = issue.project

//Comment these lines out if you are interested in sending the full list of versions and components of the source project.
replica.project.versions =
replica.project.components =
–

Note the “replica.comments = issue.comments.findAll{!it.internal}”.

This seems to work on most issues (tested couple different connections with similar config) and even some in this specific project, but for this issue the notes were synced.

Could you please help me understand what causes this? Despite our Jira being in cloud, I cannot see exalate cloudnode details for this connection (customer end is DC). Please let me know if you need more info from our end.

[Majid]

Was the comment edited by any chance? Was the config changed/ touched on either end?

[eficode.artem]

Hi Majid,
No, the comment was not edited. I think you are going for “was it changed from public to internal note” but that does not seem to be the case here.

Config was not modified.

[Majid]

No, I really meant if the comment on the source side was edited in any manner - the one that should not have gone over, but did. Its just a chain of thought at this stage to see if this is an avenue I can down while investigating it.