|
||||||||
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/d/optout.
I saw that you released version 0.5. So I did another test today.
While resetting JENKINS_DATA_HOME and installing version 0.5 instead of 0.4 this bug cannot be reproduced.
I just acknowledged another thing with 0.5:
When creating a new job, as a registered and logged in user, after confirmation of the job form the user is not owner of that plugin
see here:![]()
![]()
In (the now working) dialog of "manage owners" the plugin knows the owner very well: see here ....
the moment I wanted to take the screenshot the bug reoccured. Kind of frustrating. I hope you can reproduce that.
One thing I can confirm: If I uncheck the global option "Require Configure rights" the managing of ownership on a job is successful.