Last modified: 2014-07-22 20:43:24 UTC
If you click on "(take)" next to "Assigned To:", the assignee changes to yourself, however the original assignee isn't added to the CC List. In most cases I encounter, this is not what is wanted: I want to signal: "I'll do this!", but still keep the original assignee "in the loop". So clicking on "(take)" (and maybe "(edit)") should put the original assignee in the CC List. If this happens in JavaScript and not in the backend, it would also allow in those few cases where you want to remove the assignee from a bug altogether to erase his handle from CC List as well by editing it after taking/editing the assignee.
I can also see enough cases when the previous assignee does not want to receive notifications anymore about a ticket s/he will not work on... I don't plan to work on this; I think this should go upstream to decide.
I disagree because we'd add the default assignee to CC always and spam them.
(In reply to Andre Klapper from comment #2) > I disagree because we'd add the default assignee to CC always and spam them. I wrote in comment #0: | [...] If this happens in JavaScript and not in the | backend, it would also allow in those few cases where you want to remove the | assignee from a bug altogether to erase his handle from CC List as well by | editing it after taking/editing the assignee.
You did write that, but I disagree on the assumption that we talk about "few cases".
(In reply to Andre Klapper from comment #4) > You did write that, but I disagree on the assumption that we talk about "few > cases". I just wanted to make it clear to any casual observer that I am not one of "we" in the "we'd [...] spam them". Now if only bug #28339 had already been resolved and we had some hard data what the few and what the many cases are ... (Provided that comment #4 is now your final reasoning and not comment #2 with which you resolved this bug.) But as this bug was about not wasting my time more than necessary: "Keep calm and carry on."
I'm afraid Bugzilla does not allow querying "Assignee was X; then X was added to CC field?" against the same X value. :( (Another small issue we'd need to sort out: If a ticket became access-restricted and the default assignee was moved to CC, bugmail notifications would still be public.)
