|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I agree with Jarek. It shouldn't change the value in the job config, but instead should just override it.
Also, I think it should throw a validation warning in the job config when you have it checked but globally disabled. Something along the lines of "This option is globally disabled by the administrator, so it will not have any effect." That way if expose password is globally disabled, the job configurations won't mysteriously change, and the user is adequately informed why it's not working like they expect.
Typically when I see a field that gets reset to the default every time I save, I think it's a bug, because it's a very common type of problem to see with plugins (configuration fields not getting saved/loaded correctly). It's probably best to avoid including that sort of behavior on purpose.