Issue Summary

When updating issue security of an existing issue through the REST API, the issue history shows the opposite and shows it is set to none. The security level is assigned to the issue but the issue history shows it wrong.

Steps to Reproduce

• Set the security level of an issue using the REST API
• Check the issue history

Expected Results

The Issue history shows the security level as to the required one.

Actual Results

The Issue history shows the security level set to "None".

 

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available.