Bug 457016

Summary: XMLRPC bugzilla.createBug does not set Priority
Product: [Community] Bugzilla Reporter: Tomas Hoger <thoger>
Component: WebServiceAssignee: Noura El hawary <nelhawar>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 3.2Keywords: Regression
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-30 20:15:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 406071    
Attachments:
Description Flags
v1 adding setpriority group membership as a condition to set priority at bug creation time dkl: review+

Description Tomas Hoger 2008-07-29 08:27:25 UTC 
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?
Comment 1 Tomas Hoger 2008-07-29 08:41:42 UTC 
The above was done using an account in setpriority group, of course ;).
Comment 2 Noura El hawary 2008-07-29 14:19:57 UTC 
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
Comment 3 Noura El hawary 2008-07-29 14:48:48 UTC 
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 4 David Lawrence 2008-07-29 15:51:11 UTC 
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
Comment 5 Noura El hawary 2008-07-30 03:48:34 UTC 
Thanks for the review Dave, committed to cvs now.
Comment 6 David Lawrence 2008-07-30 20:15:17 UTC 
Pushed to partner-bugzilla.redhat.com today.