| 2009-01-15 18:59:47 |
Graham Binns |
bug |
|
|
added bug |
| 2009-01-15 19:00:00 |
Graham Binns |
malone: status |
New |
Triaged |
|
| 2009-01-15 19:00:00 |
Graham Binns |
malone: importance |
Undecided |
Low |
|
| 2009-01-15 19:00:00 |
Graham Binns |
malone: statusexplanation |
|
|
|
| 2009-01-15 19:06:22 |
Graham Binns |
description |
At the moment, if you send an email to a Launchpad bug containing a series of commands, such as:
affects malone
status triaged
importance high
... and so on, but don't include a comment, those commands will show up as a comment on the bug.
What should happen instead is that the commands are carried out and then a normal bug change notification gets issued, sans the commands as written in the email. The commands shouldn't appear as a comment and they shouldn't be sent out with the change notification, since we're effectively sending the same email out twice and stopping Launchpad from batching the notifications up. |
At the moment, if you send an email to a Launchpad bug containing a series of commands, such as:
affects malone
status triaged
importance high
... and so on, but don't include a comment, those commands will show up as a comment on the bug.
What should happen instead is that the commands are carried out and then a normal bug change notification gets issued, sans the commands as written in the email. The commands shouldn't appear as a comment and they shouldn't be sent out with the change notification, since we're effectively sending the same email out twice and stopping Launchpad from batching the notifications up.
This becomes particularly relevant once bug history / activity logs are working properly and bug activity is interleaved with comments. |
|
| 2009-04-01 15:14:41 |
Diogo Matsubara |
tags |
|
email |
|
| 2010-06-04 09:42:58 |
Graham Binns |
tags |
email |
email story-better-bug-notification |
|
| 2012-04-10 01:44:21 |
Robert Collins |
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) |
|
| 2012-04-10 01:45:58 |
Robert Collins |
summary |
Emails with no content are shown as comments (and forwarded to all bug subscribers) |
Emails with no content are shown as comments (and forwarded to subscribers) |
|
| 2012-04-10 01:49:51 |
Robert Collins |
description |
At the moment, if you send an email to a Launchpad bug containing a series of commands, such as:
affects malone
status triaged
importance high
... and so on, but don't include a comment, those commands will show up as a comment on the bug.
What should happen instead is that the commands are carried out and then a normal bug change notification gets issued, sans the commands as written in the email. The commands shouldn't appear as a comment and they shouldn't be sent out with the change notification, since we're effectively sending the same email out twice and stopping Launchpad from batching the notifications up.
This becomes particularly relevant once bug history / activity logs are working properly and bug activity is interleaved with comments. |
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). |
|
| 2013-08-12 14:44:53 |
Mackenzie Morgan |
removed subscriber Mackenzie Morgan |
|
|
|
| 2013-08-13 02:24:53 |
William Grant |
marked as duplicate |
|
222849 |
|
| 2013-08-13 02:25:03 |
William Grant |
removed duplicate marker |
222849 |
|
|
