Emails with no content are shown as comments (and forwarded to subscribers)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Symptoms
========
If you send an email to a Launchpad bug containing nothing other than a series of commands, quotes or a signature - such as:
---
>>> yes you should do that
affects malone
status triaged
importance high
----
The email will be:
* shown as a comment in the web UI
* forwarded verbatim to subscribers to the bug
But these usually result in duplicate status change text and the like, which is unpleasant.
Analysis
========
However the email is not interesting:
* the status changes are notified via the metadata change (so redundantly)
* quotes from someone else are (nearly always) part of the discussion on the bug and already seen by other subscribers
* mail signatures have no bug-specific content
We could safely hide mails that had just commands; signatures and quotes are perhaps more contentious, but addressing them will do a much better job. It might be good to get some stats from the DB about the prevalence of quoted segments not already present in the bug history (e.g. offline conversations getting forwarded to the bug).
| Changed in malone: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| description: | updated |
| tags: | added: email |
| Dan MacNeil (omacneil) wrote | #1 |
| tags: | added: story-better-bug-notification |
| Curtis Hovey (sinzui) wrote | #2 |
| summary: |
- Emails that contain nothing but bug commands shouldn't be displayed as - comments + Emails with no content are shown as comments (and forwarded to all bug + subscribers) |
| summary: |
- Emails with no content are shown as comments (and forwarded to all bug + Emails with no content are shown as comments (and forwarded to subscribers) |
| description: | updated |
It is also a bit of noise in the bug webpage to weed through.