117932 - Data munged: Dupping bug carries over fields from other bug

Status: RESOLVED WORKSFORME

(Bugzilla :: Creating/Changing Bugs, defect, P2)

Description

[Ben Bucksch (:BenB)]

I got the following mail from Bugzilla. The Activity log page shows similar info.

<example>
http://bugzilla.mozilla.org/show_bug.cgi?id=62197

[e-mail] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
           Keywords|polish                      |helpwanted
          QAContact|[e-mail] |[e-mail]
Resolution|                            |DUPLICATE
            Summary|[RFE] Display only partial  |[FEATURE]Tree view of news
                   |names in Newsgroup Tree     |subscriptions



------- Additional Comments From [e-mail] 2002-01-03 07:40 -------
yes.

*** This bug has been marked as a duplicate of 38931 ***

</example>

The problem is that the only change I made was to type "yes" in the Comment
field, select resolve dup and enter a bug number to dup again. I did none of the
other changes, namely the keyword, summary and qa changes. I guess it was Neil
who did that before, but Bugzilla attributes it to me.

I haven't seen this bug before - what I did see before was that several
modification notifications were rolled into one, but with correct attribution, like
<example>
[e-mail] changed:
...

[e-mail] changed:
...
<example>

Comment 1

[Ben Bucksch (:BenB)]

> I guess it was Neil who did that

No, the field values are taken over from the dup bug.

Comment 2

[Dave Miller [:justdave]]

were you in the same browser window and using back etc to move between the bugs?
 and did you make similar changes to those in the other bug prior to marking the
new one a dupe?  I've seen some weird form cache bugs in Mozilla in the past
that would explain that...

Comment 3

[Ben Bucksch (:BenB)]

I don't remember anymore, apart from what you can see in the Activity Log.
However, it is my habit to use new browser windows.

Comment 4

[Matthew Tuck [:CodeMachine]]

Leave this at 2.16 ... see if anything else comes up.  I don't recall seeing
another instance of this.

Comment 5

[Dave Miller [:justdave]]

I can't think of a way to reproduce this.  Moving to 2.18 since I sincerly doubt
if we'll fix this in time for 2.16.

Comment 6

[Gervase Markham [:gerv]]

Resolve as unreproducible?

Gerv

Comment 7

[Myk Melez [:myk] [@mykmelez]]

So resolved.  Please reopen if you experience the problem again.

Comment 8

[Dave Miller [:justdave]]

clearing target on DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as
untriaged if they get reopened.