Sometimes resolved bugs are shown with a strikethrough in the bug number sometimes not. It's really annoying that it's not consistent. Strikethroughs are fx shown in the viewing of a bug but not in the bug list. Please be consistent

So, is the best way to do this to call GetBugLink() more often? I've got a patch which will do this, but I'll wait until 2.14 is out before attaching it, so it is as up to date as possible (unless anyone wants it sooner). I've added an extra parameter as well, to pass in the information which would otherwise require a DB lookup, if that information is known at the time of the call. The places where I have changed this are: 1) In the bug list 2) In the navigation_header 3) In the bug_form bugid 4) In the show_activity 'back-to-bug' link 5) In createattachment (before and after) Are there any others?

OK, I found some more... 6) in CheckIfVotedConfirmed 7) after posting a bug 8) In duplicates.cgi 9) In editproducts.cgi 10) after process bug 11) in reports.cgi 12) in sanitycheck 13) in show dependency 14) in show votes

->New product Bugzilla

We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.

These unloved bugs have been sitting untouched since June 2002 or longer. If nobody does anything else to them, they certainly won't make 2.18 Retargetting to 2.20. If you really plan to push them right now, you might pull them back in.

GavinS, is this bug still valid or can it be closed now?

(In reply to comment #6) > GavinS, is this bug still valid or can it be closed now? > I'm pretty sure this is still an issue. (But I haven't done an audit to confirm that.) I'm sure there are still places that don't use GetBugLink(), but that may be for performance reasons.

Related bugs are probably: bug#137751, bug#115658, bug#115796 (maybe a dupe of this)

This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.

Still seeing this behavior in the nightly build from 5/9/05. Is this supposed to be fixed yet?

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