BUGZILLA-SUBMIT(1)

NAME
bugzilla-submit - post bugs to a Bugzilla instance

SYNOPSIS
bugzilla-submit [--status bug_status] [--url bug_file_loc] [--product
                product] [--version version] [--component component]
                [--summary short_desc] [--hardware rep_platform]
                [--os op_sys] [--priority priority] [--severity bug_severity] [--assigned-to assigned-to] [--cc cc] [--keywords keywords] [--depends-on dependson] [--blocked blocked] [--description comment] [--no-read] bugzilla-url

DESCRIPTION

bugzilla-submit is a command-line tool for posting bug reports to any instance of Bugzilla. It accepts on standard input text resembling an RFC-822 message. The headers of that message, and its body, are used to set error-report field values. More field values are merged in from command-line options. If required fields have not been set, bugzilla-submit tries to compute them. Finally, the resulting error report is validated. If all required fields are present, and there are no illegal fields or values, the report is shipped off to the Mozilla instance specified by the single positional argument. Login/password credentials are read from the calling user's ~/.netrc file.

bugzilla-submit accepts a single argument: bugzilla-url. Its value must match the relevant Bugzilla instance's base URL (technically, its urlbase param). The program also accepts the following options to set or override fields:

-b. --bug-status
    Set the bug_status field, overriding the Status header from standard input if present. (The stock Bugzilla web presentation identifies this field as ``Status''.)

-u, --url
    Set the bug_file_loc field, overriding the URL header from standard input if present. (The stock Bugzilla web presentation identifies this field as ``URL''.)

-p, --product
    Set the product field, overriding the Product header from standard input if necessary.

-v, --version
    Set the version field, overriding the Version header from standard input if necessary.

-c, --component
    Set the component field, overriding the Component header from standard input if necessary.

-s, --summary
    Set the short_desc field, overriding the Summary header from standard input if necessary. (The stock Bugzilla web presentation identifies this field as ``Summary''.)

-H, --hardware
    Set the rep_platform field, overriding the Hardware header from standard input if necessary. (The stock Bugzilla web presentation identifies this field as ``Hardware''.)

-o, --os
    Set the op_sys field, overriding the OS (Operating System) header from standard input if necessary. (The stock Bugzilla web presentation also identifies this field as ``OS''.)

-r, --priority
    Set the priority field, overriding the Priority header from standard input if necessary.

-x, --severity
    Set the severity field, overriding the Severity header from standard input if necessary.

-d, --description
    Set the comment field, overriding the Description header from standard input if necessary. (The stock Bugzilla web presentation identifies this field as ``Description''.) If there is a message body and no Description field and this option is not specified, the message body is used as a description.

-a, --assigned-to
    Set the optional assigned_to field, overriding the Assigned-To header from standard input if necessary.

-C, --cc
    Set the optional cc field, overriding the Cc header from standard input if necessary.

-k, --keywords
    Set the optional keywords field, overriding the Keywords header from standard input if necessary.

-D, --depends-on
    Set the optional dependson field, overriding the Depends-On header from standard input if necessary.

-B, --assigned-to
    Set the optional blocked field, overriding the Blocked header from standard input if necessary.

-n, --no-stdin
    Suppress reading fields from standard input.

-h, --help
    Print usage help and exit.

This program will try to deduce OS and Hardware if those are not specified. If it fails, validation will fail before shipping the report.

There is expected to be a single positional argument following any options. It should be the URL of the Bugzilla instance to which the bug is to be submitted.

FILES

~/.netrc
    Must contain an entry in which the machine field is the Bugzilla instance URL, the login field is your ID on that host, and the password field is the right password. The URL in the machine field must be enclosed in double quotes. For example, if your Bugzilla instance is at "http://landfill.bugzilla.org/bztest/", and your login and password there are "john@doe.com" and "foo", respectively, your .netrc entry should look something like:
        machine "http://landfill.bugzilla.org/bztest/"
        login john@doe.com
        password foo Note that the machine entry should match exactly the instance URL specified to bugzilla-submit.

AUTHORS

Christian Reis <kiko@async.com.br>, Eric S. Raymond <esr@thyrsus.com>.