Bugzilla/de

All bugs in the MediaWiki software should be reported at phabricator.wikimedia.org. Phabricator is also the place to request new features or enhancements to the software, while Bugzilla is the abandoned bug tracking software.

Was ist Bugzilla?
Für weitere Informationen, siehe den Wikipedia-Artikel über Bugzilla.

Bugzilla ist ein Fehlerverfolgungswerkzeug, entwickelt von der Mozilla Foundation und es ist das System, das wir benutzen um alle offenen Probleme zu verfolgen.

Die Antwort warum wir Bugzilla verwenden ist, das es Entwicklern erlaubt, schnell und einfach Fehler zu finden und Probleme zu diskutieren, um Duplikate zu erkennen und sie schließlich zu lösen.

Wikimedias Fehlerverfolger wird für gewöhnlich "Bugzilla" genannt. Eine ältere Bezeichnung wäre "MediaZilla".

Einen Bug melden oder eine Funktion beantragen
Bitte Wie man einen Bug meldet beachten.

Kommentare
Bugzilla Kommentare sind Klartext; Sie können HTML nicht nutzen. Allerdings wird Bugzilla automatisch Hyperlinks in dieser Hinsicht machen:

Link zu:


 * Fehlerbericht:


 * Kommentare: . Kann auch mit Fehler kombiniert werden:


 * Attachments:


 * SVN commits: (link to the revision shown in Code review (through Special:Code/MediaWiki))


 * Change sets in Gerrit:

The recognized format for changeset number is. Newlines added by bugzilla break the autolinking, as usual. Technical details: see rules.

Weitere Informationen unter: Hints and Tips. Von The Bugzilla Guide. Suche dort die neueste Version.

Vollständige URL
Webseiten:

MediaWiki-style internal links
They are supported. By default they point to English Wikipedia. Interwiki prefixes are supported as well and work as usual, starting from en.wikipedia.org: will link to the German Wikipedia, and so on.

Using pipes for a different label does not work. For example;  is not supported and won't create a link.

Section links work too, but you need to insert them correctly: the simplest way is to copy the URL from the location bar of your browser, and add brackets around the part of it after, e.g.  to link MediaWiki (technically: the section link has to be already URL-encoded).

Longer interwiki links need to be on their own line, otherwise they're split over two lines and won't be linkified. If an interwiki link is not recognized, add a colon : before it (e.g. ).

Since recently, also non-local interwikis work.

Why must I register?
We need you to register to use Bugzilla. This is primarily so that we can contact you if there are further questions regarding your bug submission. For example, if a developer cannot replicate your problem they will ask for more information. By default you will get e-mail notifications when there is activity on your bug reports.

You can also add/remove yourself from any bug report (including reports created by other users).

You can change your preferences to specify when Bugzilla should (and shouldn't) send emails to you. To change your preferences, log in on Bugzilla and click on your email address at the top right of the page.

How do I register?
Registering is simple and free. Click the "create account" link at the top right of the page, enter your e-mail address (and optionally your real name) and click "create account". Then simply log in using the password you receive in the confirmation e-mail (which can be changed in your preferences once you have logged in). When logging in enter your email address in the login form on any Bugzilla page.

Note that new users are prevented from taking certain actions by default, such as closing or assigning tickets. This is largely to protect against spam. You can acquire these rights by participating in the tracker in other ways, or by requesting them on IRC.

How to hide your email address
Please note that (unlike on Wikimedia projects) your email address will be visible on threads you participate in, and on thread CC lists you have added yourself to. It is visible to everyone who is logged in. It is not visible to people who are not logged in. Your email address can not be hidden from logged-in readers.

It is possible to create an additional web-based e-mail address, and then set it to forward email to your main email address. This prevents exposure of your main email address. Google Mail (Gmail) allows free email forwarding. One can automatically forward email from one Gmail account to another Gmail account, or to any email account.

You can change your email address or name at anytime on Bugzilla. They are then changed in all bug threads you participated in. So if you decide later on to hide your main email address or name you can still do so.

Why can't I report bugs on the wiki?
You could also report bugs by writing them in chalk on the pavement. However, if you want a developer to act on it then you need to put it somewhere they are likely to see it, namely Bugzilla.

How do I link to a bug?
If you want to create a link from a wiki page to a Bugzilla report, use, where XXX is the number of the bug report. For example will result in the following link: 4198.

You can also use the template, for example   will result in. In some wikis, you can use (shown to the right), and also   when the bug report has been marked as fixed.

What do the priority and severity fields mean?
Siehe Bugzilla/Fields und Bugzilla/Fields.

What does the Status field mean? (NEW, RESOLVED, etc.)
See the field description. NEW is also one of the statuses that an open bug might have.

Why can't I claim a bug or mark it resolved?
You need the "editbugs" permission, which can be granted by any person who already has it - which is most developers. Please ask in the #mediawiki IRC channel, and someone will grant it to you very quickly.

How do I grant someone the editbugs permission?
Go to the editusers interface and search for their email address, then click on their entry in the result list. You should see a checkbox next to the "editbugs" label. Check it, then click on "save changes". All done!

Queues

 * Liste offener Bugzilla-Tickets nach Anzahl der Stimmen

Siehe auch

 * Using bugzilla
 * Bugzilla/Fields – how to fill out different fields in a bug report.
 * Bugzilla products & components
 * A bug's life cycle – how the Status and Resolution fields work.
 * patch-related keywords - how to use the Keywords field to track patches (either in bugzilla or gerrit)
 * Wikipedia: Bug reports and feature requests


 * Following bugs
 * Annoying little bugs
 * wikibugs-l – mailing list to follow all Bugzilla activity.
 * #mediawiki-dev (IRC) is automatically notified with every change to Bugzilla, as well.


 * Bugzilla administration and contacts
 * Bug management
 * List of Bugzilla admins on Meta
 * Bugzilla administrator rights policy (New, June 2013)