Red Hat Bugzilla – Bug 812233
Make e-mail notification plain text by default
Last modified: 2014-10-12 18:47:37 EDT
Bugzilla 4.2 release notes highlights e-mail notifications will be sent in HTML format by default. Current <https://partner-bugzilla.redhat.com/userprefs.cgi?tab=settings> Red Hat Bugzilla testing instance confirms it.
I personally prefer plain text e-mails. I think most of the developers either.
So I propose the change default settings to plain text notifications.
You are free to change it to plain text yourself (Bugzilla->Preferences), or specify it in your mail client. The e-mail is sent with the multipart/alternative content type.
However, HTML e-mails will be the default.
This is breaking the principle of least surprise - at least the default should not have been changed for existing users after the upgrade.
The same for the crazy comment box before comments!
Reopening as plain text should remain the default for all development accounts. Breaking engineering workflows is not acceptable.
See comment #1.
*** Bug 823517 has been marked as a duplicate of this bug. ***
I agree with peterm here: If you're going to make a publicly visible change you should have indicated that this change was coming in the Bugzilla Update emails that were sent out, AND included instructions how to change it back to the previous default of text-only email.
Telling users that they can change it back isn't sufficient.
More than humans use Bugzilla. If bugbots/email parsers/automated tools expect plain text, changing the default on those tools will break them, and if a human isn't monitoring those tools, they're all going to have to track this problem down. You need to change this back and make html email opt in, at least until such time as you can announce the deprecation of the text default in favor of HTML, and give users a chance to react to the change.
Also, not all bug assignees are humans but lists. These lists now get HTML,
and I have no idea really how to log into these list accounts and change the
stuff back to what it was.
please listen to us. This change makes life difficult for 99% of engineers and breaks lots of tools. What is the reason that you are unwilling to switch the default back to what it was before?
(In reply to comment #5)
> See comment #1.
I assume we're meant to read that as in "see figure one".
This impacts me also, as my primary source of bugzilla emails is mutt MUA.
(In reply to comment #9)
> Also, not all bug assignees are humans but lists. These lists now get HTML,
> and I have no idea really how to log into these list accounts and change the
> stuff back to what it was.
If you supply the list names we can configure them as plain only. I did that for email@example.com
(In reply to comment #13)
> If you supply the list names we can configure them as plain only. I did that
> for firstname.lastname@example.org
Why not just switch the default back to non-html instead of forcing everybody including yourselves jump through hoops because of this unexplained and strange change of defaults? If somebody wants html goo in their mail they'd still have the option to have it, but I'm willing to bet most of us dealing with bugzilla believe html belongs to web pages, not email.
(In reply to comment #14)
> (In reply to comment #13)
> > If you supply the list names we can configure them as plain only. I did that
> > for email@example.com
> Why not just switch the default back to non-html instead of forcing
> everybody including yourselves jump through hoops because of this
> unexplained and strange change of defaults?
As of midnight UTC, text e-mail and additional comment below comments are the defaults.
(In reply to comment #15)
> As of midnight UTC, text e-mail and additional comment below comments are
> the defaults.
Ah... sanity :) Thank you!