-
Improvement
-
Resolution: Fixed
-
Minor
-
None
If you are using Jenkins in an intranet (or other "trusted" environment), it's usually desirable to leave this checkbox off, so that each project developer can configure their own project without bothering you.
Is horribly bad advice, and contradicts with the enabling of security by default in 2.x Jenkins IMHO
Also, the message when security is disabled is too weak.
Expected: THE HOUSE IS ON FIRE WHAT WERE YOU THINKING
Actual: Uh, you know, maybe you should consider ticking this box?
It also doesn't make sense in the now secure-by-default state, i.e. only shows when the user disabled it.