Bug management/Task list
Tasks, thoughts and ideas related to Wikimedia bug management.
Help is welcome - please contact the bugwrangler if you plan to work on an item).
- Identify and track progress of open tasks in Wikimedia Phabricator with priority set to "Unbreak now" (and to some extend to "High") and identify issues to mark as deployment blockers
- Triage new and existing reports by making sure that sufficient information is provided, setting priority if wanted by development teams, helping to find assignees, cleaning up and organizing older tickets.
- Coordinate and (co)organize bugtriage, bugsquad community outreach and growth (via bugdays)
- Improve the process of bug submission, the bug status workflow, and bug management documentation
- Keep an eye on other feedback channels where bugs might be reported, like Village Pumps, especially in the 24h after deployments of new software versions on the WMF servers
- Phabricator maintenance (to some extend; taxonomy and configuration changes)
Goals and tasks are nowadays tracked for "Aklapper" (the bugwrangler) in Phabricator. See the Developer-Relations workboard.
Anybody is free to help and work on these items.
- General bug documentation updates (please see phab:T206 first!):
- Bug documentation updates that require discussing with other stakeholders first:
- Make meanings of resolutions/statuses clearer (in Bug_report_life_cycle or How_to_triage?), e.g. when to set WONTFIX (and when not) in Bugzilla or DECLINED in Phabricator, and after how much time to close a report without enough information as WORKSFORME in Bugzilla or DECLINED in Phabricator? (This was OPW feedback from Valerie.)
- design keyword (Bugzilla)/project (Phabricator) workflow: Improvements possible? Requires talking to the design team.
- Talk to Mobile team: Are there instructions somewhere for users how to provide a stacktrace when the Wikipedia App crashes on iOS or Android that could be added to How to report a bug? (e.g. bugzilla:41027)
- Policy: Define a policy when users are blocked or when insulting/useless comments will be hidden - might not be needed as the global Code of Conduct applies
- Policy: Usually "community-consensus-needed" (keyword in Bugzilla, project in Phabricator) is used where there are concerns that the local community might not have discussed the change, or the change is not supported by them. Otherwise "shell" is used to show bugs which need a shell user to review, merge and deploy. "community-consensus-needed" is always turned into shell after clarification that community consensus exists, cf bugzilla:45539.
- Consider collecting stock answers, cf. Maemo or MeeGo
Tasks that require special permissionsEdit
Tasks listed here require special Bugzilla or Phabricator permissions (e.g. being an admin) hence only a small number of people can work on them.
- Clean up after migration to Phabricator: Duplication of information in Bugzilla: keywords vs tracker bugs vs products:
- newparser keyword vs Parsoid product: talk to James_F (James Forrester) (PM for Parsoid)
- analytics keyword vs Analytics product (and Wikimedia/Statistics) --> Contact analytics ml if they use Bugzilla and if it works for them?
- newphp keyword vs PHP4.x tracking bug 30092
- tracking keyword vs tracking meta bug 2007
- SSL: Component vs. tracking bug bug 53999
- Cleanup: Identify MediaWiki extensions in SVN which have not been converted from now read-only SVN to Gerrit and are hence dead. Close their bug reports as RESOLVED WONTFIX (Bugzilla) or DECLINED (Phabricator), explaining the situation, and add some "unmaintained" project (to be discussed and defined) so they could be identified later per component in case somebody wants to pick up development again? Also see Git/Conversion/Extensions_queue.
Finished / completed tasksEdit
Also see the weekly status updates for more verbose information.
- 20141124: Wikimedia migrated from Bugzilla to Phabricator
- 20140422: Rename "Tools" product to "Utilities" in Bugzilla - bugzilla:53986#c23
- 20140213: Puppetize Bugzilla - bugzilla:51036
- 20140213: Show common queries on Bugzilla frontpage - bugzilla:22170
- 20140213: Upgrade Bugzilla from 4.2.7 to 4.4.1 - bugzilla:49597
- 20140213: Move Bugzilla from old kaulen server in Tampa to new zirconium server in Eqiad
- 20140205: Finalize Bugzilla etiquette (Announcement)
- 20131215: Taxonomy cleanup: Move "CiviCRM" product into a "Wikimedia" subcomponent - bugzilla:57738
- 20131202: Warn that patches should go to Gerrit instead of Bugzilla - bugzilla:42606
- 20131202: Link on top of enter_bug.cgi to the guided bug entry form - bugzilla:52696
- 20131128: Port our custom patches from Bugzilla 4.2 to 4.4 - bugzilla:49597#c5
- 20131115: Decrease our custom CSS differences with upstream code (16 CSS files deleted) - bugzilla:54823
- 20131111: Renamed "shellpolicy" keyword to "community-consensus-needed" - bugzilla:49494
- 20131026: Guided bug report form for Bugzilla newbies available - bugzilla:36762
- 20131014: Enabled InlineHistory by default for all users - bugzilla:47256
- 20130930: Create good relation to upstream Bugzilla developers via attending upstream Bugzilla meetings and being active on IRC and the support-bugzilla mailing list
- 20130926: Do not limit Product column in buglist.cgi to 8 chars - bugzilla:40244
- 20130925: Show InlineHistory in Bugzilla - bugzilla:47256
- 20130901: Clean up open UsabilityInitative tickets as per bugzilla:36111#c1 and bugzilla:24335#c2. - bugzilla:52943
- 20130830: Documenting best practices in Bugzilla via blogpost miniseries -- see the list
- 20130827: Quick "Show other bug reports in this component" query link in bug report - bugzilla:46413
- 20130723: Replace "patch-in-gerrit" keyword by an automatically set status. Related: bugzilla:39399, bugzilla:39402; Discussion started on wikitech-l | Gerrit Notification Patch
- 20130614: Display "email" instead of "login" string in Bugzilla - bugzilla:24992
- 20130614: Start documenting best Bugzilla practices in a blog series linked from mw:Bug_management#Tricks_and_best_practices_in_Bugzilla List
- 20130613: Document Bugzilla administrator rights and guidelines
- 20130611: More useful Bugzilla frontpage - bugzilla:22170
- 20130508: Wikimedia Labs instance for Bugzilla at boogs.wmflabs.org created by Ori
- 20130422: Enhance "Weekly Bug Summary" email on wikitech-l to have correct data and include most urgent issues - bugzilla:45770
- 20130416: Cleanup: Closed remaining (Uniwiki extension tickets as it's unmaintained (part of cleanup bugday).
- 20130412: Enhance "Weekly Bug Summary" email on wikitech-l to have correct data and be more useful - bugzilla:45770
- 20130408: Removed "bugsmash" keyword from all Bugzilla tickets, so it could be used with its actual meaning.
- 20130326: Search tickets currently in four different components, consider simplification
- 20130322: Taxonomy: Merged several mobile apps - bugzilla:41922
- 20130319: Start having ~bimonthly IRC office hours on Bug management
- 20130211: Creation of Bug Life Cycle flowchart by Valerie, embedded in mw:Bug management/Bug report life cycle
- 20130129: First bugday, organized by Valerie and Andre
- 20130115: Finalized How to report a bug page (with help of Guillaume) for translations
- 20130111: Document how development teams use Bugzilla - mw:Bug management/Development teams usage
- 20130106: Publish list of Bugzilla admins
- 201301: Docs: Further update and clean up of bug management related documentation: Bug management Doc Rewrite
- 20121217: Smaller Bugzilla bugfixes: bugzilla:40344, bugzilla:41321
- 201212: Docs: Guidelines for creating new products in BZ
- 201212: Docs: Instructions for project maintainers how to add/change products and settings
- 201212: Docs: Document who checks BZ security updates? - Andre, documented on mw:Bug management
- 201212: Docs: "upstream" keyword policy: "Upstream ticket URL should exist when setting, documented on mw:Bug management/Upstream bugtrackers now part of mw:Upstream projects#Components
- 201212: Disable use of RESOLVED LATER resolution as as discussed
- 20121204: Upgrade Bugzilla to version 4.2 upgrade - bugzilla:33158
- Find out which extensions are deployed in production to give them higher priority when triaging - done and implement in Greasemonkey script, cf. bugzilla:36738), Category:Extensions used on Wikimedia, Gerrit
- 201111: Bigger updates to Triage guide
- 201211: Creation of "immediate" priority in Bugzilla (discussion) due to varying use of "highest"
consider introducing a status WAITINGFORUPSTREAM like in Mer Bugzilla- not wanted as per mailing list discussion, use lowest priority and "upstream" keyword instead
- 20121108: List extensions that are deployed but should get killed? User:Malyacko/ExtensionsToUndeploy
- 20121108: Rename old "MediaWiki%20extensions/Wikidata" component from OmegaWiki vs new Wikidata project - done by Chad
- 20121031: Publish Greasemonkey triage scripts
- 20121030: Docs: Create an UpstreamBugtrackers overview page: mw:Bug management/Upstream bugtrackers now moved to mw:Upstream projects#Components
Random Phabricator queriesEdit
Random Bugzilla queriesEdit
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date.
Due to Wikimedia's move from Bugzilla to Phabricator the links below are outdated and only kept for historical reasons.
- See also: wmfBugZillaPortal
- without changes for 2yrs
- No comments from anybody else than reporter
- more than 20 votes
- Open bugs for Bugzilla itself
- MediaWiki: Open && Target Milestone==1.20.x
- MediaWiki: Open && Target Milestone==1.21.0
- MediaWiki: Open && Target Milestone==1.22.0
- Latest changes in Bugzilla