Closed Bug 339820 Opened 19 years ago Closed 19 years ago

Entering an invalid assignee when amending a bug can result in loss of Comments and other changes just entered !!!!

Categories

(Bugzilla :: Creating/Changing Bugs, defect)

Product:
Bugzilla
Component:
Creating/Changing Bugs
Platform:
x86
Windows ME
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 282368

People

(Reporter: support, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90) Build Identifier: Bugzilla 2.20.1 IE 6.0.2800.1106 If you happen to make a typo in the email address of the person you are aassigning the bug to at the same time as adding comemnts, you get a "assignee xxx@yyy.com did not match anything". If, since the time of opening the original bug, you have used another IE window in the meantime to open another bug, then when you press the browser "back" button on the original winddow following trhe invalid assignee message (as there is no other UI option to do anything else) then instead of taking you back to the bug with all your changes waiting, instead it reloads a "clean" copy of the bug. In my case this meant extensive comments that I had been working on for over 2 hours were lost - very very very irritating !! Reproducible: Always Steps to Reproduce: 1. Open a bug. 2. Enter a comment and use an invalid email address as the assignee on the original bug but do not press commit. 3. Open a new IE window and open another bug. 4. Press Commit on the original bug. 5. At the "assignee xxx@yy.com did not match anything" page , press [Back] 6. You GET A RELOADED COPY OF THE ORIGINAL BUG WITH ALL YOUR CHANGES LOST ! Actual Results: Copy of bug as it was before any changes were entered. Expected Results: Back to the bug page SHOWING THE CHANGES ALREADY ATTEMPTED. Frankly, I think depending on the browser's "back" capability at this point is fundamentally weak. There should either be : 1) a REAL "back" button on the "assignee does not match" page which specifically reloads the bug including the changes that were just attempted to be committed or 2) The ability to update the assignee (or whatever email address does not match) at the point the "does not match" message is displayed. As a heavy bugzilla user, working in multiple issues all day, I find this particular design flaw very frustrating when it occurs !
*** This bug has been marked as a duplicate of 282368 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.