Default issue security level is reset when switching projects during issue creation

When customers have two Issue Permission Schemes that contain the same security level names, (for example by taking a copy of the existing scheme), the security level is changed to "None" even though the default level is something other than "None".

A screencast that illustrated the problem is attached, named: "IssueSecurityBug.mov"

This behaviour can cause unsuspecting users to create unsecured issues, even though the issues should be created with a security level by default, so this bug creates a potential security issue for customers.