Originally asked by Harold Oconitrillo on 18 April 2023 (original question)
I used the following Exalate instructions to implement syncing of issue security: https://docs.exalate.com/docs/how-to-synchronize-securitylevel-issue-field-in-jira-on-premise
This is what I added to each Jira instance:
Outgoing sync
replica.securityLevel = replica.securityLevel
Incoming sync
issue.securityLevel = replica.securityLevel
Note: I verified that the sync user (1) has the ability to set issue security in the project’s permission scheme and (2) has visibility of both of our security levels (Internal / External).
Upon changing the field, the sync completes “Synchronized” but no changes are made to the destination instance. I tested this both directions with the same result.
Tested but not working
import com.exalate.basic.domain.hubobject.v1. BasicHubIssueSecurityLevel
issue.securityLevel = new BasicHubIssueSecurityLevel(null, "name", "description")
OUTGOING SYNC includes:
replica.securityLevel = issue.securityLevel
INCOMING SYNC includes
import com.exalate.basic.domain.hubobject.v1. BasicHubIssueSecurityLevel
Same result as before, field remained unchanged.
issue.securityLevel = new BasicHubIssueSecurityLevel(null, "name", "description")
<< Correction >>
OUTGOING SYNC includes:
replica.securityLevel = issue.securityLevel
INCOMING SYNC includes
import com.exalate.basic.domain.hubobject.v1. BasicHubIssueSecurityLevel
Same result as before, field remained unchanged.
issue.securityLevel = new BasicHubIssueSecurityLevel(null, "name", "description")