[Bug 60098] New: Changing multiple bugs only allows RESOLVED as status
http://bugs.winehq.org/show_bug.cgi?id=60098 Bug ID: 60098 Summary: Changing multiple bugs only allows RESOLVED as status Product: WineHQ Bugzilla Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs@list.winehq.org Reporter: imwellcushtymelike@gmail.com CC: austinenglish@gmail.com Target Milestone: --- Distribution: --- Created attachment 81645 --> http://bugs.winehq.org/attachment.cgi?id=81645 Screenshot Before the upgrade, it used to be possible to change the status of multiple bugs at once. Mainly useful in closing bugs that aren't Wine bugs, and doing them all at once keeps the e-mail noise lumped together. Now the only option is RESOLVED. Is this a configurable option? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=60098 --- Comment #1 from Alexandre Julliard <julliard@winehq.org> --- That would depend on the status of the bugs you selected, not all transitions are allowed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=60098 --- Comment #2 from Ken Sharp <imwellcushtymelike@gmail.com> --- That's what I thought but I tried with a single resolved bug and the result is the same. There are no options but RESOLVED. Same with no bugs selected. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=60098 --- Comment #3 from Alexandre Julliard <julliard@winehq.org> --- It's based on the query, not on which bugs you selected individually. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=60098 Ken Sharp <imwellcushtymelike@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #4 from Ken Sharp <imwellcushtymelike@gmail.com> --- So it is! I'm probably remembering incorrectly. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=60098 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com --- Comment #5 from Zeb Figura <z.figura12@gmail.com> --- Though, is there a good reason to forbid some transitions? In particular, for INVALID/DUPLICATE/etc there's no good reason to not allow just going to CLOSED immediately, and forbidding RESOLVED -> NEW is annoying when someone incorrectly resolves a bug. I guess REOPENED is the intent, but it makes it sound like the bug was fixed and then resurfaced. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=60098 --- Comment #6 from Ken Sharp <imwellcushtymelike@gmail.com> --- Definitely agree with that. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=60098 Ken Sharp <imwellcushtymelike@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Ken Sharp <imwellcushtymelike@gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla