Bug 318378 - bugs.kde.org emails should explicitly discourage user replying to the mail, and ask them to use the web interface to add comments.
Summary: bugs.kde.org emails should explicitly discourage user replying to the mail, a...
Status: CONFIRMED
Alias: None
Product: bugs.kde.org
Classification: Websites
Component: templates (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDE sysadmins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-15 08:04 UTC by Jekyll Wu
Modified: 2024-07-29 20:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
prepend warning message in sent mails (807 bytes, patch)
2013-04-15 22:21 UTC, Jekyll Wu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jekyll Wu 2013-04-15 08:04:23 UTC
I know bugzilla does support that feature, but there are a few issues with it:

1. Although it doesn't happen with high frequency, I do notice that from time to time some user somehow manages to send the reply to kde-bugs-dist@kde.org without adding the comment.  So (almost) nobody will see it. Data lost. I notice that because I follow kde-bugs-dist@kde.org.

2. Another thing related with data lost is sometimes users try to upload attachment through replying the email. That sometimes works, sometimes not.  I have observed conversations like "I sent the file as attachment but where is it ? well, you should use the web interface"  between users and developers for a few times.

3. Sometimes, users choose to provide non-sensitive information in a private mail to someone whose email address is mentioned in the received mail, instead of adding it in the public tracker. I have experienced such situation quite a few times. That is really bad, not only because it creates unexpected noise for me, but also that it makes the information not as usual as is it could have been.  Information should go to the public tracker whenever possible.


4. Users have no overview concerning latest bug status, available attachments and so on. It happens from time to time some user asks "in which version is this bug fixed?", although the web interface clearly says it.

5. Uses replying the email tends to quote too much, which creates clutter in the web interface unnecessarily.


So my suggestion is in the start of each sent mail, add something which explicitly discourages users replying to this mail and encourage them to use the web interface. This is what is used in mails(excluding the ones for the original reports) sent from bugs.gentoo.org : 

    DO NOT REPLY TO THIS EMAIL. Also, do not reply via email to the person
    whose email is mentioned below. To comment on this bug, please visit:
    https://bugs.gentoo.org/show_bug.cgi?id=448686

    --- Comment #13 from someone@somewhere.com ---
    I can confirm that renaming the "old" Ebuilds to 2.6.3 works.


Note I'm not suggesting disabling that feature (bugs.gentoo.org seems to have totally disabled it by using a invalid reply-to address). I just want to discourage *average* users using it. It should still be useful and usable for *power* bugzilla users.  








Reproducible: Always
Comment 1 Jekyll Wu 2013-04-15 22:21:09 UTC
Created attachment 78943 [details]
prepend warning message in sent mails

Haven't really tested the patch, just for reference.
Comment 2 Tom Albers 2013-04-22 20:51:38 UTC
Can you test it on your local install maybe? I think the position might not be the best, as i don't think the url will follow your text, which you seem to rely on in the text...
Comment 3 Christoph Feck 2015-10-16 08:26:52 UTC
Since Jekyll is no longer active in KDE, change back status.
Comment 4 Justin Zobel 2021-03-09 05:49:41 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 5 Nate Graham 2024-07-29 20:34:35 UTC
Still valid.