Last modified: 2007-05-11 13:43:27 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 9704 - Feature request - block lengths shown in the log
Feature request - block lengths shown in the log
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-04-26 07:05 UTC by Huji
Modified: 2007-05-11 13:43 UTC (History)
0 users

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


Description Huji 2007-04-26 07:05:02 UTC
The length of previous blocks of an IP or user account plays a role on the
administrators' decision about a future block. Nevertheless, the block history
(logs) doesn't specify this, after a block is finished. 

For those blocks which has been terminated by "unblocking" the user, the lengthe
can be estimated by calculating the time difference of "block" and "unblock"
records in the log. However, for blocks which were finished when their duration
was due, there is no systematic way to estimate this duration.

It would be a wise idea to add a feature to record the block lengths in the
block summary automatically. It would be even more appreciated, if the length of
previous blocks could be pulled out from the database and shown in the details
of that record in the logs.
Comment 1 Huji 2007-05-11 13:43:27 UTC
I was mistaken. It was already supported and needs activation on our side, merely.

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