71606 - new e-mailtech doesn't show which bug a bug is being duped to

Status: VERIFIED FIXED

(Bugzilla :: Bugzilla-General, defect)

Description

[Daniel Bratell]

I just got a mail from bugzilla saying:

[e-mail] changed:

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE 


With the old e-mail you could see which bug it was getting duped to (hand
shortened old mail):

  ! Status: NEW   
  ! Resolution: 
  --- 3,10 ----
  ! Status: RESOLVED   
  ! Resolution: DUPLICATE
  ***************
  *** 157,159 ****
  --- 157,164 ----
  + ----- Additional Comments From [e-mail]  2000-07-14 15:42 ---
  + 
  + 
  + *** This bug has been marked as a duplicate of 40203 ***

Comment 1

[Daniel Bratell]

Btw, that was bug 71604 and it didn't store anything about which bug it was
duped on in the visbile part of the bug report anyway - so it might be something
else than the e-mail tech that is at fault.

Comment 2

[Andreas Franke (gone)]

This should be a 2.12 blocker, too.

Comment 3

[Andreas Franke (gone)]

Dave, could it be that this is related to your checkin to process_bug.cgi (rev.
1.78) on Mar 10 16:53 ? It seems that landfill doesn't show this bug, but
mozilla.org is broken (also tested with bug 66267 / bug 66268).
If mozilla.org is running the tip but landfill isn't, this would be an
explanation.

http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=process_bug.cgi&root=/cvsroot&subdir=mozilla/webtools/bugzilla&command=DIFF_FRAMESET&rev1=1.77&rev2=1.78

Comment 4

[Andreas Franke (gone)]

The CVS tip is definitively broken. Reverting process_bug.cgi to rev. 1.77 fixes
the problem for me. Reassigning to Dave, cc endico.

Comment 5

[Andreas Franke (gone)]

Dawn: Because of bug 71600 you did not receive the last comment. The good news
is that there is a "fix" (backout).

Comment 6

[Dawn Endico]

So the only problem here is that the comment is missing? My experience
yesterday was that bugs were getting marked properly in the duplicates
table. If that's the case then we're not losing any data.

i'd rather not back that out. Dave's patch fixed bug 7873, which is
more severe than this. After the problem is fixed we can mark the
affected bugs by hand.

Comment 7

[Dave Miller [:justdave]]

Ah.  The fix is to move ONE line of code. :-)   Patch coming up shortly. (See, 
aren't you glad we updated b.m.o BEFORE tarballing 2.12? - we got to find all 
these critical bugs first. :-)

Comment 8

[Dave Miller [:justdave]]

Attachment: Fix for failure to add dupe comment on the dupe

Comment 9

[Dave Miller [:justdave]]

Checked in.  Dawn, do your thing on b.m.o.

Comment 10

[Dawn Endico]

thing done

Comment 11

[Matthew Tuck [:CodeMachine]]

Verified this now works with or without a comment.

Comment 12

[Dave Miller [:justdave]]

Moving closed bugs to Bugzilla product