Bug 1342338 - The bug users roles doesn't get changed after change bug's product
Summary: The bug users roles doesn't get changed after change bug's product
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-03 03:22 UTC by Rony Gong 🔥
Modified: 2016-06-06 00:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-06 00:41:15 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1296697 0 high CLOSED "Change several bugs at once" will erroneously reset the QA Contact field to its default 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1297909 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1298602 0 unspecified CLOSED unwanted automatic reset of bug contacts on mass change 2021-02-22 00:41:40 UTC

Internal Links: 1296697 1297909 1298602

Description Rony Gong 🔥 2016-06-03 03:22:16 UTC 
Description of problem:
The bug users roles doesn't get changed after change bug's product

Move a bug to a different product, save it. We can find that all users roles doesn't changed, e.g. assingee, cc, qe, docs_contact.

Version-Release number of selected component (if applicable):
5.0.3.rh1

How reproducible:
100%

Steps to Reproduce:
1.Open a bug, then move this bug to a different product, save
2.Check the all users roles of this bug.
3.

Actual results:
No change.

Expected results:
Should change to target component's roles.

Additional info:
This work well when just changing it's component.
Comment 1 Muhammad Tahir 2016-06-06 00:41:15 UTC 
This is by design. If you want the field to be reset to default, click on edit and check the reset to default box.
Note You need to log in before you can comment on or make changes to this bug.