3 ms·
I can see why this would be annoying when a project is first being set up, but once things are underway I much prefer having individual emails for each event.
by jewel 14y ago
I can see why this would be annoying when a project is first being set up, but once things are underway I much prefer having individual emails for each event. The advantage comes when you only scan the subject line for each notification.
For example, we use trello at my day job to track projects and tasks. They offer to send emails either "periodically (once an hour)" or "instantly". Nevertheless, they still fold multiple actions into a single email if they happen in rapid succession, and send an email that says something like "2 new notifications on the board Development". I would much rather see each notification as a separate email since sometimes they are relevant to me and sometimes they aren't.
- rickyc091 14y agoI'm on the same boat. I'd rather get each permission notification individually, aside from the notifications when you add a new user to the organization. I'm assuming when a new user gets added to the org, they probably received one notification saying they've been added to so and so. If that's the case couldn't you just stick all those allowed permissions within the same email?
- rnaud 14y agoThat is also the approach that we used. Only the "like" action on our platform is bound to happened ten times or more in a row, so it is the only email delayed. Coding wise, it is a simple as setting a run_at on our Delayed::Job and a custom queue for this user notification. For every new notification we check if there is another delayed job to be procesed in that queue, if it is the case we just edit the run_at to add a few more minutes.