Hiding Issue Security field in Field Configurations prevents default security level of project Issue Security Scheme from being assigned to newly created issues

In using JIRA for the purposes of technical support, we would like to limit the visibility of issues to the Reporter and Internal Staff. We have created an Issue Security Scheme with this security level, and set the security level as the default for the Issue Security Scheme. We have then associated the Issue Security Scheme to the technical support project.

The presence of the Issue Security field on the screen unnecessarily raises the anxiety level of customers who fear that human error may accidentally reveal their issues to other customers. So as to reduce this problem, we would like to hide the Issue Security field using the Field Configurations administration page. (Using the Field Configurations administration page is less work and far more preferable to customizing JIRA's webwork source code.)

Unfortunately, when the Issue Security field is hidden in the Field Configurations administration page, issues that should have otherwise been assigned a security level of Reporter and Internal Staff by default are instead created with no security level. Showing the Issue Security field restores proper function by having newly created issues assigned a security level of Reporter and Internal Staff.

I fear that this problem may also affect other hidden fields created to maintain internal information that we would choose not to show to end users.