We’re looking to optimize our Exalate synchronization in Azure. We’ve heard that adjusting sync behavior to only create new comments (and avoid editing existing ones) is generally the safest and most scalable approach.
For those of you using Exalate in Azure, what user are you typically leveraging for your Exalate integration, and have you found this ‘new comment only’ sync strategy to be effective in your environment?
Any insights or best practices regarding user permissions or sync configurations would be greatly appreciated - and if anyone has advice on how to script this, or has examples, that would be appreciated as well.
Our existing script is just the default for comments:
workItem.comments = commentHelper.mergeComments(workItem, replica)
And I am not sure how I would extend that to not “edit” comments, would this work?
workItem.comments += replica.addedComments
Or some other behavior?
Hi @Matthew_Berzinskas,
Welcome to the Exalate Community — great to have you here!
To better assist you, could you please share a few more details about your setup? Specifically, what is your remote system? For example, are you syncing with Jira (which supports comment editing), but you’d like to prevent edits on the Azure DevOps (ADO) side?
Looking forward to understand your use case in more detail so I can guide you more effectively.
Thanks,
Sonal
Yes - sorry, we have Jira work items (stories, tasks, bugs) synching to corresponding issue types in DevOps.
The issue, as I was explaining (poorly), is that when an issue comment is edited in Jira, the Exalate integration fails because its trying to update the DevOps comment, which support explained to me is not typically allowed unless you are the creator.
So the goal would be prevent edits and either just add the edited comment as a new comment (even though it will create duplicates) - potentially with a tag like [edited comment], or something else, if there are best practices.
Can you please try this script ?
Hi @Matthew_Berzinskas , I have performed testing with what Sonal has shared.
Jira Outgoing:
replica.comments = issue.comments
ADO Incoming:
workItem.comments += replica.addedComments
Result: When I edited the comment from Jira side, so it did not synchronise either as a new comment on ADO side or it did also not attempt to edit the comment on ADO side which would cause an error on ADO side. Thus, it will simply ignore the edited comment synchronisation.
In case this does not comply your requirement, then please let us know.