COS:

• Resolution
• Environment
• Security level

Testing Notes

Only plays for this type of story include:

• deleting the field when assigned
  -> this field is a system field so we can't delete it. I tried to hide it but we don't honour those settings (see https://jira.atlassian.com/browse/GHS-5831?focusedCommentId=412545&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-412545)

• restricting permission to particular users
  -> the user will see an error message saying that it is not possible to access the issue after security level configuration change and on board reload the issue will not be visible in the list

• checking behavior when naming fields as system-wide objects (Unassigned) and duplicates
  -> we can create a custom field with the same name as a system field (like resolution, environment and security level). It will be selectable in the field list in the Issue Detail View tab of the configuration page.