Closed
Bug 220339
Opened 21 years ago
Closed 21 years ago
Combined messages can be confusing
Categories
(Bugzilla :: Email Notifications, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 179351
People
(Reporter: 3.14, Assigned: preed)
Details
Attachments
(1 file)
(deleted),
message/rfc822
|
Details |
I don't know if this has been reported before, I have no idea what to look for.
Sorry about that.
I just received an e-mail (see attachment for complete message) which was
totally confusing to me. It mixes up the bug it refers to and a dependency. As
far as I can see after looking at those bugs, these are two different things
which were combined in on mail. Let me show you in detail what confused me:
> bzbarsky@mit.edu changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
OK, Boris changed the status to resolved, but resolved what?
> Bug 84887 depends on bug 38370, which changed state.
Well, OK, a blocking bug did change. How could that do the change above? It did
not, but this is how it looked to me.
> Bug 38370 Summary: Can't change <HR> and <BR> color
> http://bugzilla.mozilla.org/show_bug.cgi?id=38370
>
> What |Old Value |New Value
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> Resolution| |FIXEDBug 84887 depends on bug
38370, which changed state.
OK, great, that other bug was fixed. But why is the dependency repeated here,
this was stated above already?
> Bug 38370 Summary: Can't change <HR> and <BR> color
> http://bugzilla.mozilla.org/show_bug.cgi?id=38370
Again?
> What |Old Value |New Value
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> Resolution| |FIXED
It said so just before, why again? But waid, is that what the original bug
(84887) was changed to? After all this information was still missing. But just
above it says something about the other bug (38370).
> ------- Additional Comments From bzbarsky@mit.edu 2003-09-25 16:48 -------
> Fixed by bug 38370.
Ah, finally the comment to the first change.
So here is my suggestion how to solve it. If we want to combine different
incidents in one mail (I don't think we should, but this is not the question
here), then each incident should be given completly, seperated by a clear marker
like a line like this:
--------------------- change n ------------------------------------
pi
Reporter | ||
Comment 1•21 years ago
|
||
Reporter | ||
Updated•21 years ago
|
Attachment #132183 -
Attachment mime type: message/rfc-822 → message/rfc822
Assignee | ||
Comment 2•21 years ago
|
||
*** This bug has been marked as a duplicate of 179351 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•