Hi
Every instances that Exalate is installed upon, has full control over what data gets send and how received data gets assigned.
This means that for your use-case, you can control from which instance the comments should get sent over.
Please surf to the Outgoing Sync on your Exalate connection and look for this statement;
replica.comments = issue.comments
and you can modify this.
More info;
https://docs.exalate.com/docs/how-to-sync-comments-in-jira-cloud
Thank you.
Kind regards,
Mathieu Lepoutre
Mathieu Lepoutre maybe I didnt explain well here.
So T1 on Jira 1 is exalated to T2 (Jira2) and to T3 (Jira 3). And the whole chain actually has 6 instances.
Same T1 ticket is Exalated to multiple Jira instances.
Now if someone adds a comment to T2, it cascades to T1 (rightly) and to T3 (wrongly).
Can you please help with that?
Hello Majid 
Replicating the situation, I provide you this:
A comment gets placed in a ticket T2, it goes to T1 and T3 and lets limit the flow from T1 to T3.
The comment that gets placed in T1 will have a the author field be Exalate (your proxy-user).
This means we can filter out those comments in the outgoing sync in T1.
If you look at the Entity Sync Status in T1 of the ticket, you will see this;
"comments": [
{
"id": "10504",
"author": {
"key": "557058:c020323a-70e4-4c07-9ccc-3ad89b1c02ec",
"active": true,
"email": "com.exalate.jiranode@connect.atlassian.com",
"displayName": "Exalate"
},
"updateAuthor": {
"key": "557058:c020323a-70e4-4c07-9ccc-3ad89b1c02ec",
"active": true,
"email": "com.exalate.jiranode@connect.atlassian.com",
"displayName": "Exalate"
},
"body": "Admin commented: this ticket only to parent",
"created": 1692789334638,
"updated": 1692789334638,
"internal": false,
"restrictSync": false
},
So to filter it out, please go to the Outgoing Sync for the connection to T3 and put this there;
issue.comments = issue.comments.findAll { it.author.displayName != "Exalate" }
replica.comments = issue.comments
Please change Exalate to the displayName of your proxy-user.
Please let me know how it goes.
Thank you.
Kind regards,
Mathieu Lepoutre
We have a single Jira Cloud ticket syncing with many target Jira Cloud tickets (on different instances). Lets say ticket 1 (on instance 1), syncing to ticket 2 (on instance 2) and ticket 3 (on instance 3). When a comment is made on Ticket 2, it come back to ticket 1 (that is fine), but then it goes to ticket 3 as well.
How can we control this behavior?