Skip to main content

Report bug

2 replies [Last post]
Joined: 2009-11-03

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2010-06-04

Reporting a bug
You've got a bug, and you're itching to report it. The first thing you should do is search for an existing bug. Someone may have already reported the bug. Searching first helps to prevent duplicates. To be effective, try multiple synonyms and rephrasings of what the bug might have been called.

The next step is to create an account, as accounts on Wikipedia do not carry over into bugzilla. Your email address will be visible on any report you make and on any votes you cast.

Finally, you get to enter your bug! Select the product (usually MediaWiki), and you're ready to go.
[edit] Details

Here are what the fields mean (for MediaWiki):

* Version - for bugs visible on Wikipedia, choose 1.16-svn
* Platform and OS - these usually have no bearing on the actual bug, but it doesn't hurt to leave them specified (if you don't, 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:
o Blocker - blocks development and/or testing work (you probably wouldn't know)
o Critical - crashes, loss of data (internally, not, say, your edit preview)
o Major - major loss of function
o Minor - minor loss of function, or other problem where easy workaround is present
o Trivial - cosmetic problem like misspelled words or misaligned text
o 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 fewer. Be pithy, be precise, and 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.

[url=]Mercedes Benz LS Parts[/url]

Jan Luehe wrote:
> Does anyone know how to report bugs?

Use GlassFish issue tracker at,
subcomponent: "webcontainer"


> [Message sent by forum member 'mohammadalavi']
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail: