Bug 805770 - Flag.update() function can't update attachment flag
Summary: Flag.update() function can't update attachment flag
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: WebService
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: 4.2-2
Assignee: Simon Green
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 497464
TreeView+ depends on / blocked
 
Reported: 2012-03-22 04:26 UTC by Tony Fu
Modified: 2018-12-09 06:29 UTC (History)
2 users (show)

Fixed In Version: 4.2.1-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-31 22:12:58 UTC


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.