Description of problem: bugzilla.createBug in new BZ does not seem to set bug Priority according to what is requested, but rather use default value. Example, following test bug: https://partner-bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-3231 Was created using request: $VAR1 = { 'priority' => 'urgent', 'version' => 'unspecified', 'bug_file_loc' => 'http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-3231', 'keywords' => 'Security', [ ... ] 'alias' => 'CVE-2008-3231', 'bug_severity' => 'urgent', 'op_sys' => 'Linux' }; Severity is set correctly, priority value uses default - medium. According to extensions/compat_xmlrpc/code/webservice.pl, such priority usage should still be valid: "priority" => "urgent", # OPTIONAL Valid priority from the list of priorities. # Ex: medium Can this be somehow related to the fact that enter_bug.cgi does not seem to allow setting priority?
The above was done using an account in setpriority group, of course ;).
This is basically because the parameter: letsubmitterchoosepriority is set to off in partner-bugzilla when i set it to on i was able to set priority at bug creation time, this is actually a different behavior to bugzilla 2.18 caze currently in the live bugzilla we still have that param set to off but we can still set the priority at creation time. Noura
Created attachment 312877 [details] v1 adding setpriority group membership as a condition to set priority at bug creation time checking the difference in the code between bz2.18 and bz 3.2 basically , in bz2.18 if the UserInGroup('setpriority') or the letsubmitterchoosepriority is set to on then user will be able to set priority at bug creation time , but in 3.2 we only have the condition letsubmitterchoosepriority is set to on if that is not true then user will not be able to set priority. not sure if we want to add this redhat customization at bug creation time regarding the setpriority group but in case we decide to attached is a patch to do so. Noura
Comment on attachment 312877 [details] v1 adding setpriority group membership as a condition to set priority at bug creation time Yes, we want to retain the behaviour from 2.18. Patch looks good to me. Dave
Thanks for the review Dave, committed to cvs now.
Pushed to partner-bugzilla.redhat.com today.