|
I added a comment to
Error messages are now displayed if the Security Level field is mandatory and not set or set to "None".
If the field is not set - the error message relays the information that the "Set Security Level" permission is required in order to set this field. Also, an actual security level must be chosen - "None" is not accepted. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Major
Making Security Level required doesn't do anything
The problem does occur if the user does not have permissions to set levels, there are levels and the issue level field is marked reuqired. Is this what you are refering to? 
One thing - I believe it might be a known 'issue'. If the user picks none from the drop down, even if the field is made required then we do create an issue with no level. We treat none as a value for the field. So this is a 'feature'
The problem does occur if the user does not have permissions to set levels, there are levels and the issue level field is marked reuqired. Is this what you are refering to?