Opened 7 years ago

Last modified 7 years ago

#1734 new improve feature

Email notifications of new messages, only one per day

Reported by: TimLoal Owned by:
Priority: minor Milestone:
Component: BW Mail Keywords: Message Email Notifications


Granny Christelle, commented today that 'when several people send me a message the same day, I get only one alert for the more recent message I received this day.'

I have noticed this in the past, but I must admit it is not the most used part of the site for me.


Change History (8)

comment:1 Changed 7 years ago by TimLoal

This is actually quite a sneaky one, because with less frequent messaging, you learn that you reliably get an email from bW for each message. Then you get into a conversation and send two or more messages in the same day you don't get the second email notification and assume there is no second message and have no notification on the messages link on each page of new messages, so don't check there. (I'll open a ticket for that)

So many of the UX bugs are simple details like this, not big things. What brings bW down is there are so many of them and like this are unreliable and non user supporting, which users don't like. If a bus service, seemingly randomly, took different routes. You could never use it and be sure where you'll end up! To be fair these issues are falling in number fast and have come down a lot, but we need to change what is normal on bW. Normal should be really great! Soon! :)


comment:2 Changed 7 years ago by TimLoal

  • Priority changed from minor to major

Escalating to Major as it sounds fairly easy to find and fix. So is low hanging fruit.

Also due to the public view of this issue. It would be nice to be able to solve it quickly and improve our image with the members. Its all about patterns. If members see patterns they like they will be happier to come back and use bW more often. If not they wont. Its about as simple as that.


comment:3 Changed 7 years ago by TimLoal

  • Milestone changed from Future to 1.0

Move to milestone 1.3 if not suitable on 1.0


comment:4 Changed 7 years ago by jsfan

  • Milestone changed from 1.0 to unassigned

comment:5 Changed 7 years ago by TimLoal

  • Milestone changed from unassigned to Future
  • Priority changed from major to critical

comment:6 Changed 7 years ago by jsfan

  • Priority changed from critical to minor

comment:7 Changed 7 years ago by jsfan

  • Type changed from bug to improve feature

comment:8 Changed 7 years ago by jsfan

  • Milestone Future deleted

Milestone Future deleted

Note: See TracTickets for help on using tickets.