Jump to content

Wikipedia:How to report a bug: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Zen-master (talk | contribs)
create from Wikipedia:Bug report
 
fix link to current documentation
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Soft redirect|mw:How to report a bug}}
{{Shortcut|[[WP:BUG]]}}
[[Image:BugzillaLogo.png|right]]
'''Reporting bugs''' for [[MediaWiki]] (the software that runs Wikipedia) is a process that occurs mostly in [[Bugzilla]]. Posting bugs and problems on the wiki is unlikely to recieve developer attention, so it is worth learning how to use Bugzilla to submit and comment on bugs.


== External links ==


'''related link'''
* [http://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla Etiquette at Mozilla]
#[[Wikipedia:Bug reports and feature requests]]
* [http://bugzilla.mozilla.org/page.cgi?id=bug-writing.html Bug Writing Guidelines at Mozilla]
#[[Wikipedia:MediaWiki/DeveloperMemo]]
* [http://www.bugzilla.org/ Bugzilla's home page]
* [http://bugzilla.wikimedia.org/page.cgi?id=fields.html A Bug's Life Cycle]

== Etiquette ==

Bugzilla 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. "I REALLY WANT THIS BUG FIXED!" With that in mind, please keep the following rules in mind when using Bugzilla (partially borrowed from [http://bugzilla.mozilla.org/page.cgi?id=etiquette.html Mozilla's Bugzilla Etiquette]):

* Contribute useful comments; useless comments (i.e. advocacy) increase 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 WONTFIX decisions
* Applicability varies, but when in doubt, follow the rules

If you see someone not following these rules, politely mention it to them via private email: do not bugspam some more by chastising the user for their conduct publicly.

== Reporting a bug ==

You've got a bug, you're itching to report it, first thing you should do is [http://bugzilla.wikimedia.org/query.cgi search for an existing bug]. More likely than not, someone has already reported the bug before you: searching like this helps prevents duplicates.

So... you've tried your search, trying multiple synonyms and rephrasings of what the bug could have been. Now... it's time to [http://bugzilla.wikimedia.org/createaccount.cgi create an account], as accounts on Wikipedia do not carry over into Bugzilla. Now, it's time to [http://bugzilla.wikimedia.org/enter_bug.cgi enter your bug]. Select the product (usually MediaWiki), and you're ready to go.

Here are what the fields mean (for MediaWiki):

* '''Version''' - for bugs that are happening on Wikipedia, the selection 1.6-cvs is usually correct, as Wikipedia runs code straight from the CVS repository.
* '''Platform''' and '''OS''' - these usually have no bearing on the actual bug, but it doesn't hurt to leave them specified (they are autodetected)
* '''Component''' - try to figure out what part of MediaWiki the bug is part of.
* '''Severity''' - how severe the bug is. This should not be an opinion on your part, rather, based on these tags:
** ''Blocker'' - blocks development and/or testing work (you probably wouldn't know)
** ''Critical'' - crashes, loss of data (internally, not, say, your edit preview)
** ''Major'' - major loss of function
** ''Minor'' - minor loss of function, or other problem where easy workaround is present
** ''Trivial'' - cosmetic problem like misspelled words or misaligned text
** ''Enhancement'' - request for enhancement (feature requests)
* '''Assign To''' - the field will automatically get filled, don't touch it
* '''CC''' - this field will add people to a mailing list which notifies users when a bug has been changed. It's generally not a good idea to randomly add people to the CC list (let them do it)
* '''URL''' - a specific URL for the bug, if any
* '''Summary''' - describe the bug in 60 characters or less. Be pithy, be precise, be concise, be concise. A developer should be able to read the summary and say, "Oh, that's what the bug is about." A bad summary is "Wikipedia isn't working!" Remember, people searching for bugs will often search the summary. Make a good impression: the summary should tell the developer whether or not to look into the bug.

=== Description ===

In a description, you should describe ''anything and everything'' about the bug. A general template to go about doing this is:

# An overall description of the bug
# Steps to reproduce
# Expected result
# Actual result
# Additional information

Keep things to one bug to a report, and if necessary, file multiple bug reports. A good bug report is:

# Reproducible - if the developer can't reproduce the bug, it'll get marked WORKSFORME or INVALID
# Specific - make isolating the bug to an area quicker for the developer

== Voting ==

Voting is a mechanism that allows you to show which bugs you care about. Bugs you vote for automatically send you email when they're status change. You can vote for a bug by clicking "Vote for this Bug" but remember, just because a bug has [http://bugzilla.wikimedia.org/show_bug.cgi?id=57 84 votes] doesn't mean that the developers are obligated to fix it (or that a fix will happen anytime soon).

== Linking ==

You can link to bugs from the wiki using the <code>bugzilla:</code> prefix, i.e. [[bugzilla:1000]].

== Useful queries ==

* [http://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&product=MediaWiki&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=enhancement&order=bugs.bug_id Search for all enhancement requests]
* [http://bugzilla.wikimedia.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&keywords_type=allwords&long_desc_type=substring&short_desc_type=allwordssubstr&type0-0-0=noop&y_axis_field=votes&width=620&height=350&action=wrap&format=table Reports by number of votes]

Latest revision as of 10:44, 14 January 2019