Last modified: 2014-01-24 18:45:07 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 60401 - Tags for reviews
Tags for reviews
Status: RESOLVED DUPLICATE of bug 35534
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2014-01-24 18:44 UTC by Derk-Jan Hartman
Modified: 2014-01-24 18:45 UTC (History)
5 users (show)

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


Description Derk-Jan Hartman 2014-01-24 18:44:30 UTC
I've noticed that a common cause for reviews getting stuck is often that it is stuck on 1 particular knowledge field. "This review needs someone with database expertise"

So my idea is adding an option to mark a review with tags "javascript, db, ops" and instead of having dashboards on repos, have dashboards on those tags.

This would require a bit of Gerrit work I assume, but i think it is one of the ways of solving a few of the review problems that we have seen so far.
Comment 1 Kunal Mehta (Legoktm) 2014-01-24 18:45:07 UTC

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

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