Bug 1081947 - Assignee, QA Contact and Docs Contact are not added to CC on cloning
Summary: Assignee, QA Contact and Docs Contact are not added to CC on cloning
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Simon Green
QA Contact: Matt Tyson 🤬
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-28 09:25 UTC by Jiri Benc
Modified: 2014-10-12 22:52 UTC (History)
6 users (show)

Fixed In Version: 4.4.4021
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-07 00:30:32 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1005780 0 None None None Never

Description Jiri Benc 2014-03-28 09:25:36 UTC 
When cloning bug, the original assignee is not added to the CC list of the new bug. He should be, as he's the most important person to be notified about the clone, especially when it's a clone of the same problem for a different product version.

I wonder I haven't hit this before, it may well be an issue of a particular bug report? Noticed this with bug 1077053, tried to clone bug 744655.
Comment 1 Jason McDonald 2014-03-31 03:16:15 UTC 
I can reproduce the behaviour described above.  The behaviour is not specific to the particular bug that was being cloned.

Currently, the CC-list of the clone will be the merger of the follwoing:
a) the CC-list of the original bug
b) the Reporter of the original bug
c) the default CC-list of the component that the user chooses for the clone.

The Assignee, QA Contact and Docs Contact of the original bug are not currently added to the CC-list of the clone.

For Bug 744655, the Reporter and QA Contact were both already in the CC-list and the Docs Contact was empty, which may have made it look like only the Assignee was being omitted from the CC-list of the clone.

Changing the current behaviour to add one or more of the Assignee, QA Contact and Docs Contact to the CC-list when cloning a bug has implications for the visibility of bugs with restricted access.  Currently, a bug's Assignee, QA Contact or Docs Contact who is not a member of any of the groups that a bug belongs to will not have visibility of the clones of that bug unless they are also on the CC-list of the original bug at the time it is cloned.  Addressing this bug report would mean that those users would start to gain visibility of newly cloned bugs that they would not previously have been able to view.

I therefore need to seek some policy advice from Red Hat's Security Response and Information Security teams before we can decide whether to submit a fix for this bug report.
Comment 5 Simon Green 2014-05-05 05:26:33 UTC 
Filed a bug upstream. Once they approve it, we can backport it, and then add the docs_contact on it.
Comment 6 Simon Green 2014-07-07 00:30:32 UTC 
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

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