In bugzilla.redhat.com, when someone closes ticket as duplicate, users, subscribed to this ticket, aren't re-subscribed to another one ticket automatically. Here is one of the latest examples: This ticket was closed as duplicate: https://bugzilla.redhat.com/show_bug.cgi?id=521597 But I was need to re-subscribe myself manually to that one: https://bugzilla.redhat.com/show_bug.cgi?id=521703 Here is another pair (actually, there are lots of such examples): https://bugzilla.redhat.com/show_bug.cgi?id=496051 (closed as duplicate) https://bugzilla.redhat.com/show_bug.cgi?id=494737 (original ticket, and no one subscriber from previous ticket was subscribed to it automatically).
Here it is, again! These tickets were just closed as duplicates: https://bugzilla.redhat.com/show_bug.cgi?id=522963 https://bugzilla.redhat.com/show_bug.cgi?id=522876 but nobody, except original reporters of closed tickets, were subscribed to that ticket! https://bugzilla.redhat.com/show_bug.cgi?id=521703
Hi Peter, We can consider this as a feature request, it has been discussed upstream in the following bug: https://bugzilla.mozilla.org/show_bug.cgi?id=108983 Noura
Description of problem: https://bugzilla.redhat.com/show_bug.cgi?id=623742 was marked a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=624297 Therefore, the 48 CCs of #623742 should have been added to #624297 (which only has 22 CCs at the moment). Version-Release number of selected component (if applicable): Bugzilla 3.63+ As per my understanding this is supposed to happen. Not sure why it didn't happen here. A lot of activity happened on both bugs, and looks like they were both marked dups of each other at times and reopened. Keeping that in mind, CC updating should still work.
*** Bug 650779 has been marked as a duplicate of this bug. ***
Reason we didn't do it already is because we wanted to see what the outcome upstream was related to the correctness of adding users to another bug that they may or may not want to be added. Seems like you said that it has stalled out and never came to a decision. We could look at doing this as an opt-in style feature where people can set their user preferences to allow it to happen automatically if they want. Technically it is not difficult it is just we want to make sure it doesn't upset anyone.
We will inherit this change is upstream do it. As it stands users on the CC: list will receive a notification when a bug is marked as CLOSED/DUPLICATE and may which to manually subscribe to the other bug. -- simon