224916 - Per user pref to send a summary (digest) of a bug when they're first bugmailed about a bug

Status: RESOLVED DUPLICATE of bug 546558

(Bugzilla :: Email Notifications, enhancement)

Description

[timeless]

Undigested thoughts on the matter:
> see, one feature i want out of mozmail is the ability to digest a selection of
emails. but that won't help people who don't have the old bugmails.
> although, would it be useful for people to get a digest just the first time
they are cc'd? (or each time they're cc'd) that flavor of the feature is
something even *i* would use :o. i.e. a bug goes through 5 changes before
someone cc's me. when i'm first cc'd, it'd be useful for me to get a digest of
the bug's life
< definitely
> but once i'm cc'd, i don't need the full history, just the updates
* timely notes that implementing this to work for timeless@ is actually painful
> but at least for the typical case, it'd be a cool and relatively simple feature
* timely ponders the timeless@ case
> justdave: how privacy conscious are people? some people tend to cc me on bugs
because they think i'm not aware of them. i'm not very privacy conscious, so i'm
willing to propose the following, but i need to know if people would scream:
allow each bug to keep a public list of people who have been emailed about it.
if we had that, then 1. people wouldn't keep cc'ing me to bugs that i already
get bugmail for :). and 2. timeless@ would be solvable (minus edge cases i don't
care about) for the first digest.

Digested version:
I. (user pref), create a preference to send a full bug digest to the user when
the user transitions to being considered for bugmail for a bug. (Wording could
use improvement.)

The goal is that:
1. a bug is filed
2. the bug is assigned to Tim
3. Tim reassigns to Les
4. Les comments a few times
5. Les reassigns to Tim

Tim and Les should be able to get a large bugmail each time they're assigned the
bug (Tim: 2, 5; Les: 3) but while they're continually getting bugmail, they only
need and should be able to get incremental bugmails (Tim: 3, Les: 4, 5).

I-variant. It might be better for the user to be able to get the history as an
additional email distinct from the email for the change that resulted in their
first bugmail.

II. (optional, suggested way to implement I), create a table containing bug# and
userids that would track people who have gotten mail without not being
considered for the delivery of mail since when they first received mail. (boy
that's complicated.)
what this means:
1. timeless@b is cc'd to a bug and doesn't get mail because cc'ing isn't enough
to get mail. at this time timeless@b isn't added to the table.
2. someone comments in the bug which triggers mail to timeless@b, timeless@b is
added to the table for the bug.
3. someone changes a field which doesn't trigger mail to timeless@b. timeless@b
is not removed from the table because bugzilla knows that it considered sending
mail to timeless@b.
4. someone removes timeless@b from the cc list for the bug. timeless@b got mail
and is still in the table.
5. someone comments in the bug. bugzilla recognizes that timeless@b was not
considered for bugmail and removes timeless@b from the table.
6. someone cc's timeless@b - see 1.

Some pieces of the above are probably subject to negotiation. My real case
involves timeless@m watching timeless@b and generally not caring about CC
changes at all.

II-variant. timeless@b should be added at step 1, and if timeless@m wants/needs
digests, timeless@m will have to check the [x] bugmail me when i'm added items.
When this feature is implemented, and if it's implemented in that alternate way,
i'd probably check those boxes.

III. (optional; conflicts with II-variant), Allow logged in users to view the
table from II.
Reason: People often want to know if someone knows about a bug, it's much more
convenient if they can just find out from bugzilla. Note that this would not
work well with II-variant.

Comment 1

[alanjstr]

Well, we already have the Bug Activity link, plus people can log in to read
anything they've missed.  Is this saying that once you're CC'd, you get the bug
history and comments all mailed to you?  Because if I then CC timely on a dozen
large bugs, he gets mailbombed.  

If you just want to see "who knows about this bug," that's a different situation.

Comment 2

[Joel Peshkin]

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

Comment 3

[J. Paul Reed [:preed]]

Kick all my Bugzilla bugs back to the component default owner.

Comment 4

[Frédéric Buclin]

Due to timeless inability to make short comments, I'm duping it this way...