#1384 Batch email notifications
Roll up consecutive ticket changes, wiki changes, etc into one email per artifact. The delay to wait for more changes should be 5 minutes.
there appear to be pretty big delays in getting email notifications from Allura, do we know why?
12:43
rcopeland
the delays are because we'd intended to batch them all up and send in a digest form
the batching happened; the digesting, not so much
12:58
Dave
hm, digesting isn't really useful at all for me
if there's a good use case for it, seems like it should be a user pref
12:59
rcopeland
well, one of the goals is also to roll up multiple changes to one artifact into one notification
which does seem useful
1:00
Dave
sure, as long as you don't wait too long to send it out
5 minutes maybe, not hours
1:00
rcopeland
yeah
agreed
1:14
Mark ramm-christensen
yea
5 min is what I asked for, way back 6 months ago
also that allows for things like multiple wiki page edits to be rolled into one notification
1:16
rcopeland
I think it was implemented as '5 minutes that the mailbox has no new messages'
where it should be '5 minutes that the mailbox has no new messages for that artifact'
1:16
Mark ramm-christensen
I do think there is a use case for batching, but a lot of work would have to go into designing the "what' happened today in allura" message
ahh
that was max, who is gone a long time
So here is the core issue: notification batching "worked" but only for non-message notifications (such as when changing a wiki page). The decision was made to NOT batch message notifications (such as comments, which it turns out is where all ticket changes go) so that you could reply to them individually via email.
So I'm going to put this ticket in limbo till we decide what we really want to do.
Originally by: scoop
+1 for at least consolidating a single update by one person to one ticket in one form (e.g. a comment and an owner change) into one email notification.