How can anyone look into an issue based on this description? No link to a release, no screenshot, no description of what was done!? There are dozens of tickets about ISEs with the Release Editor and I close them all if there are no reproducible steps.

This issue was opened per request by warp (http://chatlogs.musicbrainz.org/musicbrainz-devel/2011/2011-07/2011-07-26.html#T18-20-38-795516). I think he can relate the log he got to this bug.

Yeah, I entered a bare thing because warp was supposed to put the stack trace in here. Apparently he didn't, whether he forgot or he decided it was fixed, I don't know. I don't have much more info anyway, except that it was when trying to enter the edit, and that (as I found after adding this) going back to the Release Information tab and then back to Edit Note allowed me to enter it correctly. But yeah, without the log info this is pretty useless, I wonder why he didn't add it...

Ok, fine - but really, there's more than just warp who reads through the bug tracker and since we ask of this kind of information from anyone else logging a ticket, I don't think it's unreasonable to require it here - especially when you're essentially getting preferential access A stack trace isn't always enough to solve a problem.

Without a description of how to reproduce it, it's also impossible for anyone to test the fix.

(Oops, accidental reporter change)

(Sorry, comment overlap with you Nicolás - probably roughly on the same page!)

Marking for next milestone so warp can see if he still has the stacktrace - or close it if not

I'll close this as Cannot Reproduce. I may still have the stack trace, but not on a computer I currently have access to.

If the problem occurs again, feel free to re-open this and add more details, or just open a new ticket.