The bugzilla Mail interface allows the registered bugzilla users to submit bugs by sending email with a bug description. This is useful for people, who do not work inhouse and want to submitt bugs to the bugzilla system.
I know, show me the example-mail !
Please don't refuse to send one or two wrong mails, you will get all the information you need in the replies, and only in the mail replies. The information on this page, concerning available products, versions and so on, is not dynamicly generated and may be old therefore.
|Keyword||Value description||required and default value|
|@product||The product which has a bug||yes.
This is the most important information. Many other fields depend on the product.
|@component||the desired component which is affected by the bug||yes.
As the @product, this is a very important field.
|@version||The version of the product||yes.
See @product and @component
|@short_desc||A summary of your bug report||yes.
This summary of the error you want to report describes what happen. You may skip the long description, but not this summary.
Note:The short description may be given in the mail subject instead of using the keyword !
|@rep_platform||The desired platform||no.
If you don't give a value, this field is set to All.
|@bug_severity||The severity of the bug||no.
If you don't give a value, this field is set to normal
|@priority||The priority of the bug||no.
If you don't give a value, this field is set to P3
|@op_sys||The operating system||no.
If you don't give a value, this field is set to Linux.
|@assigned_to||The one to whom the bug is assigned to||no.
There is a default assignee for every product/version/component. He owns the bug by default. The default assignee can only be found if product, version and component are valid.
|@groupset||rules the visibility of the bug.||no.
This value defaults to the smallest of the available groups, which is readInternal.
|@qa_contact||the quality manager for the product||no.
This value can be retrieved from product, component and version
But most of them need valid values.
Sorry, you will not find lists of valid products, components and the other stuff here. Send a mail to with any text, and you will get a list of valid keywords in the reply.
Some of the values must be choosen from a list:
After you have specified the required keywords and maybe some other value, you may describe your bug. You don't need a keyword for starting your bug description. All text which follows the keyword block is handled as long description of the bug.
The bugmail interface is able to find required information by itself. E.g. if you specify a product which has exactly one component, this component will be found by the interface automatically.
@product = Bugzilla @component = general @version = All @groupset = ReadWorld ReadPartners @op_sys = Linux @priority = P3 @rep_platform = i386 This is the description of the bug I found. It is not neccessary to start it with a keyword. Note: The short_description is neccessary and may be given with the keyword @short_description or will be retrieved from the mail subject.