Originally asked by Björn Gullander (Riada) on 25 November 2019 (original question)
I just can’t get the Issue security to be updated in the remote Jira issue.
I have:
* exactly the same name of the Issue security scheme
* exactly the same name of the Issue security level
* Sync user is member of the Administrators role which have “Set Issue Security” permission
* Security level is set to Default level
Answer by Francis Martens (Exalate) on 25 November 2019
Has the proxy user access to the security level
Ie - if you have security level ‘Reporter and Team’, where team is a specific group, is the proxy user member of that group?
I will try to reproduce
What version of Jira
What version of Exalate
Local sync or remote sync
Comments:
Björn Gullander (Riada) commented on 26 November 2019
I think I found the error - the security level names were actually a bit different. "Supplier … " in one server an “Suppliers …” in the other.
However a follow up question - there was no error logged and no exception to be caught when I had this problem. For us it is utterly important that the security level is synced, or the wrong suppliers will see issues they should not see. Is there any other way to make sure to catch this kind of problem with security level sync?
In our case we only have one security level and it should always be set on the issues.