User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Build Identifier: When making changes to a bug, e.g., changing the severity, the assignee, resolution or such, these changes are lost without any message if I also attach a file through "Create a new attachment". This forces multiple updates and really ticks my users off if they added extensive information in the "Additional Comments" field that they want to supplement with an attachment, e.g., screen shot. Reproducible: Always Steps to Reproduce: 1. Open bug to edit 2. Change information on the showbug.cgi page (enter comment, change severity) 3. Click on "Create a new attachment" and add an attachment of any kind without adding a comment. 4. Submit change and go back to the bug. Actual Results: Only the attachment was added, all other changes and updates are lost. Expected Results: It should have kept the updates to the other field. If a comment was added in "Additional Comments" field it should (ideally) show in the comment field on the attachment.cgi page. This was not happening in 2.14.x which I was working with at my previous company.
Versions tested: 2.18.rc1 and rc2
*** Bug 345508 has been marked as a duplicate of this bug. ***
Please note that any navigation away from a changed web page reproduces this except when users click on submit. AJAX attachments would help resolve this, but implementing onUnload that would call a routine that would check if the user is leaving without using commit having updated the form (possibly by comparing the list of default values versus the list of actual values). This is generally not critical in most places except when filing or updating a bug. Users (especially new users) often forget they're using their browser and think they're using the Bugzilla application rather than accessing Bugzilla via their browser.
Correction, onUnload would fix the issue given the circumstances listed above.