Bug 831916

Summary: the new ExternalBugs.update_external_bug() can't update ext_bz_bug_id and ext_bz_type_id
Product: [Community] Bugzilla Reporter: Tony Fu <tfu>
Component: WebServiceAssignee: Simon Green <sgreen>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2CC: ebaak, sgreen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-14 05:03:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tony Fu 2012-06-14 04:58:53 UTC
Description of problem:


the new RPC call ExternalBugs.update_external_bug() can't update ext_bz_bug_id and ext_bz_type_id
How reproducible:

Always


Steps to Reproduce:
1.Using the ExternalBugs.update_external_bug() function to update an external tracker's info for a specific bug (I used bz-web2-test.devel.redhat.com as the bz stance), for example

$call = $rpc->call('ExternalBugs.update_external_bug', {ids=>[6683],ext_bz_type_id => 72,  ext_description=>'migrate', ext_bz_bug_id => '15223'});

2. Go to the bug which supposes to be updated and check External tracker section
3.
  
Actual results:
the Summary of external tracker has been updated, but tracker type (ext_bz_type_id) and ID (ext_bz_bug_id) hasn't been changed.

Expected results:

the tracker type and id should be changed to the new values.


Additional info:

Comment 1 Simon Green 2012-06-14 05:03:43 UTC
The correct solution is to delete the existing tracker and add a new one. Information like the status, priority, etc would be tainted, so not being able to update the type and id is very intentional.

  -- simon