Wikipedia:Bug reports and feature requests
![]() | This help page is a how-to guide. It explains concepts or processes used by the Wikipedia community. It is not one of Wikipedia's policies or guidelines, and may reflect varying levels of consensus. |
Bug reports and feature requests (collectively called tasks) relating to the MediaWiki software that powers Wikipedia, should be filed on Wikimedia's Phabricator. Phabricator is a software suite that includes tools for bug reporting and project management. The bug report management tool of Phabricator is called Maniphest.
Bug reports and feature requests that are not directly related to the MediaWiki software should be discussed at Wikipedia:Village pump (technical). When in doubt, discuss issues at the Village pump before filing a task on Wikimedia's Phabricator.
Updates on your task
By default you will be emailed with updates on the status of your task. Sometimes developers may reject or misunderstand a bug report or feature request and close a report that you think is still valid. If you believe there's still an issue, you can add a comment and try to make a better explanation, or you can take it to the mailing list. If you do not want to get updates on your bug, you can state this in your email preferences.
Tokens
Tokens in Phabricator can be used to show which bugs you care about. You can add a token to a report by clicking "Award Token" in the sidebar at the top of a report.
Note that developers are not obligated to implement a request just because it has a large number of tokens.
Etiquette
Phabricator is a place to notify developers of bugs and contribute information that would be useful in the fixing of the bugs. It is not a place for advocacy viz (e.g. "I REALLY WANT THIS BUG FIXED!") With that in mind, please keep the following rules in mind when using Phabricator:
- Contribute useful comments; useless comments (i.e. advocacy) decrease the signal-to-noise ratio
- The developers are under no obligation to fix your bug or add a feature you want.
- No personal abuse: do not make threats like "I will not edit Wikipedia until this bug is fixed"
- Don't mess around with fields unless you are the bug's assignee or you know what you are doing; instead, comment on the suggested change
- Don't whine about "declined" decisions
- Applicability varies, but when in doubt, follow the rules
If you see someone not following these rules, politely mention it to them via their talk page or private email: do not bugspam some more by chastising the user for their conduct publicly.
Linking to bugs from Wikipedia
{{tracked|T1000}}
creates the first right-floating box -->>
If you would like to note the fact that the task has been resolved, you can note its status via {{tracked|T1234|resolved}}
. See the second right-floating box -->
If you enable the "Enable tracking bugs on Phabricator using the {{tracked}} template" gadget in your preferences, you will always see up to date statuses for Phabricator references that use the {{tracked}} template (even if the template call omits the status or has not been manually updated).
You can link to bugs using the phab:
interwiki prefix. For example, type [[phab:T1000]]
for phab:T1000. The phab:
prefix can be used for linking to any static page in Wikimedia's Phabricator. For example, type [[phab:project/query/all/]]
for phab:project/query/all/.
Note that [[bug:T1000]]
links to the Buginese Wikipedia, not to Phabricator or its predecessor Bugzilla.
Links from within Phabricator
Links on Phabricator can either use full URL syntax like on Wikipedia (https://en.wikipedia.org/wiki/Main_Page
displays the full URL) or a wikilink-like syntax with two brackets and a full URL for a link text version ([[https://en.wikipedia.org/wiki/Main_Page|the main page of the wiki]]
displays as "the main page of the wiki"). Markdown link syntax is also supported. Other linking methods besides those are not supported.
Software deployment schedule
New software on Wikimedia is deployed regularly, usually weekly. Group 0 wikis have their main software changes deployed on Tuesdays (test websites except Test2 Wikipedia, and mediawiki.org), group 1 on Wednesdays (Catalan, Hebrew, and Italian Wikipedias, Test2 Wikipedia, and all non-Wikipedia sites), and group 2 (the rest) on Thursdays. English Wikipedia is in group 2, meaning it receives the main weekly deployment on Thursdays. There are other changes that happen on a different schedule. The current MediaWiki version is 1.45.0-wmf.3 (bd73486).
If you are experiencing a technical problem with editing or reading on Thursday or Friday which was not present earlier, the cause of that technical problem is likely the recent deployment of software. You can report problems using the guidance on this page or on WP:VPT. If you decide to report the problem on VPT, consider looking for similar issues (usually separate sections toward the bottom of the table of contents/page); you may not be the first person to encounter the issue, and it is good to keep issue discussion in one place. Sometimes the "problem" is the result of a deliberate action to change how the software behaves, so while you can provide a report, there is no guarantee it will be fixed the way you expect, if it needs fixing at all.
When filing a bug in Phabricator for regressions that appear to be related to the new MediaWiki version, please also mention it on that week's "train blocker" deployment bug.
Glossaries
- Category:Glossaries of computers
- Glossary of computer terms
- Manual:Glossary – MediaWiki
- Wikipedia:Glossary
- List of computer term etymologies
See also
- Category:Wikipedia feature requests
- User:Novem Linguae/Essays/Steps to reproduce - tips for filing a good bug report
- Wikipedia:Debugging templates
- connectivity issues
External links
- Wikimedia Phabricator, used for Wikimedia and MediaWiki bug reports and feature requests
- MediaWiki.org page about Phabricator, including user help
- The bug report life cycle
- How to create a good first bug report
- meta:Community Wishlist Survey, an annual solicitation of feature requests from the Wikimedia community
- Phabricator home page – where bugs in upstream Phabricator itself are worked on