You need to test your work before you move it to production. (Yeah, I know, you have.)
It is one of the hazards of QA testing that it is easy to focus on major functions of new code without bothering to be concerned about small functional bugs that don't seem to be too troublesome. Yet, it is often these small, apparently minor hiccups that will ultimately drive users mad with annoyance. A brand new car with a great paint job, smooth engine, comfortable seats, and great sound system is going to feel like a P.O.S. if you have to jiggle the USB connection to get it to recognize your phone, or the trunk lid rattles all the time.
Right now I am noticing that this new mail doesn't like to take action on multiple emails at one time. (Example, I select four unread emails and go to "mark as read", only one gets updated as read.) It's a small thing, really, but it is annoying as ****. Quit using your customers as your QA team. Fix it. All of it. Then try again. I'm going back to my old Mail. (Which, apparently, you guys can't keep up and running this week either)
Bradley Eaton
shared this idea