When you make a change to an attachment, you get the summary of the bug. You should also get the summary of the attachment.
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.
Changing default owner of Email Notifications component to JayPee, a.k.a. J. Paul Reed (firstname.lastname@example.org). Jake will be offline for a few months.
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Created attachment 252286 [details] [diff] [review] patch for tip
Comment on attachment 252286 [details] [diff] [review] patch for tip >+ – [% desc FILTER html %] desc is undefined.
Created attachment 252541 [details] [diff] [review] patch for tip i dont care how to show it.
Comment on attachment 252541 [details] [diff] [review] patch for tip This makes text flow awkwardly. Example: Changes to attachment 6 [details] - Test! of bug 42 submitted I think attachment description should be shown with a title just like bug description is. Most likely easiest way is to make use of a get_attachment_link filter. First, access to it will need to be provided and possibly a version that just links to edit page instead of two links.