Bug 623116 - Change of component via webservice does not change the assigned_to and qa_contact
Summary: Change of component via webservice does not change the assigned_to and qa_con...
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: WebService (Show other bugs)
(Show other bugs)
Version: 3.6
Hardware: All Linux
low
medium vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-11 11:30 UTC by Shreyank Gupta
Modified: 2013-06-24 01:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-25 20:46:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Shreyank Gupta 2010-08-11 11:30:42 UTC
Description of problem:

Change of Product and component for a bug to another, does not affect the assigned_to and qa_contact for the bug. Ideally it should get reassigned to the default owners and qa_contact (if any) for the new component/product.

I have checked that it happens when the required change occurs through web interface. It should behave similarly with the webservice. Otherwise one has to independently query the component owners and update bug, which is a specific overhead.

Comment 1 David Lawrence 2010-08-25 17:58:26 UTC
The Bug.update API has two parameters that can be passed in called 'set_default_assignee' and 'set_default_qa_contact' that if set to true will do what you are asking. If you do not set those are do not explicitly pass in new values for 'assigned_to' and 'qa_contact', the old values will be left alone.

Dave

Comment 2 Shreyank Gupta 2010-08-25 20:46:23 UTC
(In reply to comment #1)
> The Bug.update API has two parameters that can be passed in called
> 'set_default_assignee' and 'set_default_qa_contact' that if set to true will do
> what you are asking. If you do not set those are do not explicitly pass in new
> values for 'assigned_to' and 'qa_contact', the old values will be left alone.

This works. Thanks.


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