https://bugs.winehq.org/show_bug.cgi?id=48001
Bug ID: 48001 Summary: Additional Comment tool changes resolution on its own. Product: WineHQ Bugzilla Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs@winehq.org Reporter: mail@marekpasnikowski.name CC: austinenglish@gmail.com Distribution: ---
During discussion in a bug report a sign of a bug in Bugzilla appeared in this comment:
https://bugs.winehq.org/show_bug.cgi?id=47987#c9
I never intended to do any changes to anything in there besides posting further comments.
https://bugs.winehq.org/show_bug.cgi?id=48001
--- Comment #1 from Ken Sharp imwellcushtymelike@gmail.com --- Were you using the back button by any chance? Or have any kind of autocomplete add-ons for your browser?
https://bugs.winehq.org/show_bug.cgi?id=48001
--- Comment #2 from Marek Paśnikowski mail@marekpasnikowski.name --- I used and use no such tools or techniques.
I wrote comments by hand and pressed "save changes".
https://bugs.winehq.org/show_bug.cgi?id=48001
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Additional Comment tool |Status can be changed |changes resolution on its |accidentally |own. | Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #3 from Ken Sharp imwellcushtymelike@gmail.com --- I have just seen something very similar with the following process:
1. Add a comment and change the status. 2. Add an attachment. 3. Add a new comment.
For reasons unknown the status has gone back to its previous selection. If I hit "Save Changes" then this will change the status of the bug. However, if I hit refresh first then the updated Status is shown correctly.
If I then add a new comment and hit "Save Changes" then the Status is not affected.
Plain Google Chrome, in my case.
Now it's a case of figuring out if the browser, Bugzilla or the server is to blame.
Note that the new comment and the new attachment IS shown in the bug report, so the page has apparently refreshed already. It's not clear why another refresh of the page would be required to show the correct status.