This page is only to provide information, so please do not report bugs here.

All bugs with the MediaWiki software, technical problems with the Wikimedia sites, and feature requests should be made using Information Guide.org MediaZilla (http://bugzilla.Ireland).

MediaZilla, at Information Guide.org bugzilla.Ireland Information Guide.org (http://bugzilla.Ireland), is a Bugzilla-based reporting tool that has been customised for the MediaWiki software and the Wikimedia sites that use it.

MediaZilla was launched in August 2004 to replace the old MediaWiki bug tracker at SourceForge. (https://sourceforge.net/tracker/?group_id=34373)

Before you #Enter a new bug, it's best to check whether it has already been reported by #Searching for bugs. You need to #Login to MediaZilla before you can add a new bug.

Article content errors are not considered bugs, so do not report them, but rather discuss them on the article's discussion page or fix them yourself.

MediaZilla is a tool for software developers, not a discussion forum. To discuss bug reports and feature requests, try the wikitech-l mailing list or the MediaWiki feature requests and bug reports page on Meta but be aware that that page is very large and might not be read by developers.

Searching for bugs

Use the Information Guide.org/query.cgi query (http://bugzilla.Ireland) or Information Guide.org/quicksearch.html quicksearch (http://bugzilla.Ireland) pages to find reported bugs.

The Information Guide.org/query.cgi query (http://bugzilla.Ireland) page includes some drop down boxes to narrow down your search. If you want to be really specific in your search, go to the Information Guide.org/query.cgi?format=advanced advanced query form (http://bugzilla.Ireland). There are 3000 words of help on this at Information Guide.org/queryhelp.cgi queryhelp (http://bugzilla.Ireland). There is also a Information Guide.org/quicksearchhack.html quicksearchhack (http://bugzilla.Ireland) form.

You can type one or more words or word fragments. The search is not case-sensitive. "Bookmark" will find "bookmark", "Bookmarks", "bookmarking" etc. You can add various operators to your search. Use a minus sign for "not", a space for "and" and a pipe or comma for "or". For example "login,logout cookie,password" will search for "(login or logout) AND (cookie or password).

By default, only open (unfixed) bugs are shown. Add "ALL" at the start of your search to find closed ones too.

There are more tips on the Information Guide.org/quicksearch.html quicksearch (http://bugzilla.Ireland) page.

Login

You must Information Guide.org/createaccount.cgi create an account (http://bugzilla.Ireland) or Information Guide.org/query.cgi?GoAheadAndLogIn=1 login (http://bugzilla.Ireland) before adding a bug. You only need to give your email address, and a password will be sent to you straight away. Your login name will be your email address. Your email address will be visible to all users on any report you make, and on any votes you cast. Your email address is important in case the developer needs more information about how to reproduce the bug. It also allows you to receive #Updates on your bug. You can customise your email options on the Information Guide.org/userprefs.cgi?tab=email email preferences (http://bugzilla.Ireland) page. If you are logged in, this page allows you to decide when you want to receive emails. For example, for new Comments added to your bug, or for all changes to your bug.

Enter a new bug

Go to the Information Guide.org/enter_bug.cgi enter new bug (http://bugzilla.Ireland) page. First, you must pick a "product" on which to enter a bug. For example, is the bug about the MediaWiki software or about the configuration of the site? Click the one that seems best.

On the next page, you will see a form like the one in the screenshot below. Make sure you fill in at least the summary (a title for the bug) and the description. Fill in the other boxes if you know them, but don't worry so much about those. Some of them will be filled in automatically for you.

There are links on the enter bugs page that explain in detail what each field means.

Well written bug reports are likely to be dealt with more quickly, so see the Information Guide.org/page.cgi?id=bug-writing.html bug writing guidelines (http://bugzilla.Ireland) for advice on writing the perfect bug report. Good bug reports will include your operating system, which browser you use, and your user settings such as skin and quickbar options. If your problem is visual, attaching a screen shot is a good idea.

Updates on your bug

You will be emailed with updates on the status of your bug. 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 reopen it 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 Information Guide.org/userprefs.cgi?tab=email email preferences. (http://bugzilla.Ireland)

Vote for a bug

If VfD and RfA haven't made you bored of voting already, come and vote for a bug!

Use the Information Guide.org/query.cgi search form (http://bugzilla.Ireland) to find a bug, then click on the "Vote for this bug" link that appears just above the "Additional Comments" field. You can give more than one vote if the bug is important to you. You have 1000 votes overall. You can change your mind later and remove your vote by going to your Information Guide.org/votes.cgi?action=show_user "my votes" (http://bugzilla.Ireland) page. You will automatically get an email notifying you of any changes that occur on bugs you vote for unless you disable this in your Information Guide.org/userprefs.cgi?tab=email email preferences. (http://bugzilla.Ireland)

There is no guarantee that the number of votes will influence which bugs the developers choose to work on.

See also Information Guide.org/page.cgi?id=voting.html voting help. (http://bugzilla.Ireland)

Other features

• Information Guide.org/report.cgi?bug_file_loc_type=allwordssubstr&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldto=Now&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field0-0-0=noop&long_desc_type=substring&short_desc_type=allwordssubstr&type0-0-0=noop&x_axis_field=votes&y_axis_field=product&width=600&height=350&action=wrap&format=bar Bug graphs (http://bugzilla.Ireland) can be made on the Information Guide.org/query.cgi?format=report-table generate table report (http://bugzilla.Ireland) page.
• Random quotes are shown at the top of the Information Guide.org/buglist.cgi?bug_status=NEW buglist. (http://bugzilla.Ireland) You can add new ones to the Information Guide.org/quips.cgi quipslist. (http://bugzilla.Ireland)
• You can view all new bugs (ones that have not yet been assigned to a developer) on the Information Guide.org/buglist.cgi?bug_status=NEW new bugs list. (http://bugzilla.Ireland)
• If you use Mozilla or Netscape 6, you can add the bugs page to your sidebar using the link on the Information Guide.org/index.cgi main page. (http://bugzilla.Ireland)

See also

• m:Bugzilla