61246 - Automatically add old owner to CC when owner changes

Status: NEW

(Bugzilla :: Extension Ideas, enhancement, P3)

Description

[selmer (gone)]

It seems like 99% of the time, the correct thing to do on an owner change is to
add the old owner to the CC list.  It would be cool if this happened
automatically since people often forget it.  Perhaps a personal pref would
control whether any given individual experienced this since some might never
want this behavior.

Comment 1

[Jacob Steenhagen]

OK  :)

*** This bug has been marked as a duplicate of 28676 ***

Comment 2

[Dave Miller [:justdave]]

This ain't a dupe, Jake...  he's talking owner, not reporter.  The bug you marked 
this a dupe of (and is already fixed) does not fix this.

Comment 3

[Dave Miller [:justdave]]

Just to clarify what's being asked for on this bug...

If you reassign a bug to a different owner, the original owner should get added 
to the CC automatically.  He's also suggesting a preference since there may be 
occasions when you don't want this, but most of the time you do, and people 
forget.

Comment 4

[Jacob Steenhagen]

Goodness... I really misread that one.  Sorry.

Comment 5

[Matthew Tuck [:CodeMachine]]

I suggest this might be an intermediate screen, or a checkbox under the action
line when you choose to reassign the bug.

Comment 6

[Andreas Franke (gone)]

-> Bugzilla product, Changing-Bugs component, reassigning.

Comment 7

[Dave Miller [:justdave]]

*** Bug 179837 has been marked as a duplicate of this bug. ***

Comment 8

[Ludovic Dubost]

Attachment: Auto CC Patch

Implementation of this feature..

Comment 9

[Frédéric Buclin]

*** Bug 234544 has been marked as a duplicate of this bug. ***

Comment 10

[Frédéric Buclin]

*** Bug 122480 has been marked as a duplicate of this bug. ***

Comment 11

[Frédéric Buclin]

Each user should be free to decide if he wants to be added to the CC list when
someone (or himself) reassigns his bugs. Travis is working on a user preferences
table. This is the kind of pref which should go in.

I might take this bug as soon as bug 98123 is fixed (which may be in the near
future now).

Comment 12

[Frédéric Buclin]

*** Bug 311275 has been marked as a duplicate of this bug. ***

Comment 13

[Frédéric Buclin]

The trunk is now frozen to prepare Bugzilla 2.22. Enhancement bugs are retargetted to 2.24.

Comment 14

[Frédéric Buclin]

This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".

Comment 16

[:Gijs (he/him)]

(In reply to comment #11)
> Each user should be free to decide if he wants to be added to the CC list when
> someone (or himself) reassigns his bugs. Travis is working on a user preferences
> table. This is the kind of pref which should go in.
> 
> I might take this bug as soon as bug 98123 is fixed (which may be in the near
> future now).
> 

What if the old owner is not (very) active, or an unowned account (ie, bugzilla itself seems to have some fake accounts for the default assignee). If I take a bug, I should be able to decide whether I want them to remain CC-ed, given they can't decide for themselves. In this case, I'd probably want them CC-ed given the fact that lots of people watch those accounts.

Additionally, I don't believe the bug I filed (bug 365276) is really a dupe - I don't want this to happen whenever I take a bug - if I take a bug from the bug page I can do it myself if need be - but only if I take it from the attachment page, which means, as I detailed quite clearly in the bug I filed, it takes another operation to keep the old owner in the CC list, which is annoying. I should be given the opportunity to make that change from the attachment page.

Comment 18

[Max Kanat-Alexander]

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?", and either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

Comment 20

[Frédéric Buclin]

We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.