Wikimedia's Bugzilla installation is used to track problem reports and feature requests related to MediaWiki code, other Wikimedia-specific components (such as extensions or tools), and Wikimedia wikis (such as Wikipedia).
Sorting and solving bug reports is a collaborative effort by users and developers of the community together with Wikimedia's bugwrangler.
Status[edit | edit source]
Andre Klapper and Quim Gil prepared and organized Wikimedia's participation in Google Code-In. This includes supporting mentors and students by writing documentation and importing tasks. Code-related, Andre cleaned up Wikimedia Bugzilla's custom CSS by removing 16 CSS files with 6 left to stay, prepared and tested patches for upgrading Wikimedia Bugzilla from version 4.2 to 4.4, updated the Greasemonkey triagescripts (e.g. stock answers to ping assignees), and sync'ed the "WeeklyReport" Bugzilla extension code with upstream. WMF's Operations team installed new SSL certificates for bugzilla.wikimedia.org. The "shellpolicy" keyword in Bugzilla was renamed to "community-consensus-needed" and the "wikidata" keyword was removed. Furthermore, Andre created a draft for a Bugzilla etiquette.
Activity scope[edit | edit source]
Bug management is a perennial activity. Anyone can contribute! Activities include:
- coordinating, triaging, and organizing the current bug reports in Bugzilla
- writing documentation for bug management
- coordinating MediaWiki deployments
- consider developing a friendly way (perhaps an extension) to allow Wikipedia users to report problems and record them in Bugzilla
Documentation[edit | edit source]
Note that this is work in progress.
For Bug Reporters[edit | edit source]
For Module Maintainers[edit | edit source]
For Developers[edit | edit source]
For Triagers / Bugsquad Community[edit | edit source]
- Project:WikiProject Bug Squad
- Triage: Definition of "triaging" and information on bug triage sessions
- Triage guide: How you can help to improve bug reports, and tools to save time triaging
- Easy tasks and entry points to start triaging in Bugzilla
- Bugsquad meeting / Bugday preparations
- Places (Village Pumps, forums) to regularly check for bug reports
- List of upstream bugtrackers and URLs
For Bugzilla Administrators / the Bugwrangler[edit | edit source]
- Admins: Please file a report when changing products/components/keywords to avoid work duplication and entropy and to understand reasonings. This excludes trivial changes like component descriptions or assignees/CC lists.
- Status updates of the Bugwrangler (Note: The bugwrangler is employed by the Wikimedia Foundation to do bug management, see scope above)
- Plans and ideas of things to do in bug management - help welcome!
- How to run IRC office hours on bug management
- Bugzilla administrator rights policy
- Technical information on our Bugzilla instance
- Andre Klapper keeps an eye on upstream Bugzilla security updates, Daniel Zahn helps deploying them.
For everybody (General / Misc)[edit | edit source]
- An introduction to Bug report management in Wikipedia
- Bug report life cycle: The status changes of bug reports, from reporting to closing them.
- Fields in the Bugzilla interface
- Workflow: Proposal for a new workflow on problem entry that would lead the user to OTRS, RT, or Bugzilla as appropriate
Tricks and best practices in Bugzilla[edit | edit source]
A series of blog posts (in progress):
- Autocompletion (2013-06-14)
- Changing the columns in search results (2013-06-21)
- Getting copies of another user's bugmail (2013-06-28)
- Searching for empty fields (2013-07-05)
- Saved and shared searches (2013-07-12)
- Creating reports and tables (2013-07-19)
- Simpler searching for open tickets only (2013-07-26)
- Using flags to track branches and versions (2013-08-02)
- Excluding less important reports from search results (2013-08-16)
- Triage helper tools: Greasemonkey scripts (2013-08-23)
- Reports: Tickets closed last week by resolution (2013-08-30)
- To be continued...