Last modified: 2012-12-16 11:59:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T44292, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42292 - Log Changes in product/component structure of Bugzilla
Log Changes in product/component structure of Bugzilla
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
wmf-deployment
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 33158
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-20 15:30 UTC by Andre Klapper
Modified: 2012-12-16 11:59 UTC (History)
3 users (show)

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


Attachments

Description Andre Klapper 2012-11-20 15:30:19 UTC
PROBLEM:
From time to time some admins make changes in Bugzilla's
product/component structure (renaming components, renaming/deleting
keywords, creating new components, etc).
Bugzilla does not have any logging of such actions so it's pure luck
when other admins become aware of them.
Sometimes I see good reasons to disagree with changes that got applied
and I would love to discuss these changes before reverting them, but
currently I simply cannot find out know who to discuss with. :)


SLIGHT IMPROVEMENT:

http://www.bugzilla.org/releases/4.2/release-notes.html lists

Auditing of All Changes Within Bugzilla

Most changes made through the admin interface are now logged to the database, in the audit_log table. There is no UI to access this table yet, but developers are free to create their own tools to track changes made into their installation. This is only a first step, and improvements are expected in future releases.
Comment 1 Andre Klapper 2012-12-16 11:59:01 UTC
Fixed by 4.2 upgrade.

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


Navigation
Links