Bug 805770

Summary: Flag.update() function can't update attachment flag
Product: [Community] Bugzilla Reporter: Tony Fu <tfu>
Component: WebServiceAssignee: Simon Green <sgreen>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.6CC: ebaak, sgreen
Target Milestone: 4.2-2   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.2.1-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-31 22:12:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 497464    

Description Tony Fu 2012-03-22 04:26:36 UTC
Description of problem:


The rh bz xmlrpc function Flag.update() can not update attachment flag, although its documentent states "allows you to update flag (including attachment's flag) for one or more bugs."


Steps to Reproduce:
1.call the Flag.update() function like
$call = $bz_rpc->call( 'Flag.update', {
        ids => [$bug_id],
        updates => [{
            name => $new_name,
            status => $new_status,
            attach_id => $attach_id,
            
        } ]
    });

  
Actual results:
The attachment flag is not updated

Expected results:
The attachment flag should be updated to the new status value


Additional info:
Updating bug flags works well.

Comment 1 Tony Fu 2012-03-22 04:56:27 UTC
The function in oncoming bz 4.2 doesn't work either.

Comment 2 Simon Green 2012-05-17 03:45:36 UTC
(In reply to comment #1)
> The function in oncoming bz 4.2 doesn't work either.

This is a Red Hat customisation, so the upgrade isn't going to make it work by itself.

  -- simon

Comment 4 Simon Green 2012-05-17 05:49:29 UTC
Can now be tested at https://release2.bugzilla.devel.redhat.com/

Will be part of the Bugzilla 4.2.1-2 release fortnight today.

  -- simon

Comment 5 Simon Green 2012-05-31 22:12:58 UTC
This change is now live.

  -- simon