Last modified: 2005-12-23 15:53:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 4367 - Rollback with comment
Rollback with comment
Status: RESOLVED DUPLICATE of bug 3552
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-12-23 05:09 UTC by Joel Nothman
Modified: 2005-12-23 15:53 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Joel Nothman 2005-12-23 05:09:11 UTC
I have seen a number of instances where sysops have made rollbacks that should have been 
commented to specify a reason for the rollback. Usually this button will be used for 
reverting vandalism or testing, but sometimes there are borderline cases, such as 
factual inaccuracies. Adding a comment in the edit summary of the rollback helps users 
who later review the history, or users whose work was rolled back.

I would think any of:
* An edit box next to the rollback button
* A javascript popup on clicking "(w/c)" (with comment) next to rollback button
* An edit box next to the rollback button which appears when "(w/c)" is clicked
would be appropriate
Comment 1 Ævar Arnfjörð Bjarmason 2005-12-23 05:11:59 UTC

*** This bug has been marked as a duplicate of 3552 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links