The "edit attachment" screen has enough problems that it should be redone right.

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.

Blocking several 2.16 bugs, thus this should be 2.16.

I guess this falls in with completing the template stuff, so making it a blocker. (Not to mention it actually blocks a number of other 2.16 bugs :)

Summary of problems (from dependent bugs): bug 97729: obsolete own attachments. Patch by bbaetz. bug 97825: relies on Mozilla bug. Status uncertain; the Moz bug is fixed but Bugzilla still works. bug 97868: "Edit" -> "Manage" in the Actions. bug 101770: larger comment box bug 110461: inline-image for non-IFRAME browsers bug 122301: XMLSerializer abuse. Those last two are definitely not 2.16 issues. The rest are reasonably easy - the only decision is how to format the screen with a new, larger, comment box. Gerv

ping...

I don't think that this is a 2.16 blokcer, personally. Some of the dependants possibly are, but rewriting to fix xmlserialiser usage isn't something we want to do at this time, I think.

I agree. Moving out, unless Myk has a burning desire to do this, in which case he can move it back in. The current system is in use on b.m.o and works fine. Gerv

myk: what's the status here, given that the current screen has now been in use for two years without too many complaints? Gerv

Not a blocker. Gerv

All 2.18 bugs that haven't been touched in over 60 days and aren't flagged as blockers are getting pushed out to 2.20

This is old, has no response comment from myk, and is actually an enhancement. :-) We have a nice new attachments screen, FWIW. I think that this can probably be resolved as a duplicate of something, or maybe now as INVALID.

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.

WFM per comment 11 and another two years.