bugzilla(1) User Commands bugzilla(1)NAMEbugzilla - command-line interface to Bugzilla over XML-RPC
SYNOPSISbugzilla [options] [command] [command-options]
DESCRIPTIONbugzilla is a command-line utility that allows access to the XML-RPC
interface provided by Bugzilla.
command is one of:
* login - log into the given bugzilla instance
* new - create a new bug
* query - search for bugs matching given criteria
* modify - modify existing bugs
* attach - attach files to existing bugs, or get attachments
* info - get info about the given bugzilla instance
GLOBAL OPTIONS--help, -h
show this help message and exit
--bugzilla=BUGZILLA
bugzilla XMLRPC URI. default: https://bugzilla.redhat.com/xml‐
rpc.cgi
--bztype=BZTYPE
Bugzilla type. Autodetected if not set. Available types:
Bugzilla3 Bugzilla32 Bugzilla34 Bugzilla36 Bugzilla4 RHBugzilla3
RHBugzilla4 NovellBugzilla
--user=USER
username
--password=PASSWORD
password
--cookiefile=COOKIEFILE
cookie file to use for bugzilla authentication
--verbose
give more info about what's going on
--debug
output bunches of debugging info
‘NEW’ OPTIONS
--product=PRODUCT, -p PRODUCT
REQUIRED: product name (list with 'bugzilla info -p')
--version=VERSION, -v VERSION
REQUIRED: product version
--component=COMPONENT, -c COMPONENT
REQUIRED: component name (list with 'bugzilla info -c PRODUCT')
--comment=COMMENT, -l COMMENT
REQUIRED: initial bug comment
--short_desc=SHORT_DESC, --summary=SHORT_DESC, -s SHORT_DESC
REQUIRED: bug summary
--os=OP_SYS, -o OP_SYS
OPTIONAL: operating system (default: Linux)
--arch=REP_PLATFORM, -a REP_PLATFORM
OPTIONAL: arch this bug occurs on (default: All)
--severity=BUG_SEVERITY
OPTIONAL: bug severity (default: medium)
--priority=PRIORITY
OPTIONAL: bug priority (default: medium)
--url=BUG_FILE_LOC, -u BUG_FILE_LOC
OPTIONAL: URL for further bug info
--cc=CC[,CC,...]
OPTIONAL: add emails to initial CC list
--blocked=BUGID[,BUGID,...]
OPTIONAL: add bug_ids blocked by this bug
--dependson=BUGID[,BUGID,...]
OPTIONAL: add bug_ids that this bug depends on
--full, -f
output detailed bug info
--ids, -i
output only bug IDs
--extra, -e
output additional bug information (keywords, Whiteboards, etc.)
--oneline
one line summary of the bug (useful for scripts)
--raw raw output of the bugzilla contents
--outputformat=OUTPUTFORMAT
Print output in the form given. You can use RPM-style tags that
match bug fields, e.g.: '%{bug_id}: %{short_desc}'
‘QUERY’ OPTIONS
--bug_id=BUG_ID, -b BUG_ID
specify individual bugs by IDs, separated with commas
--product=PRODUCT, -p PRODUCT
product name, comma-separated (list with 'bugzilla info -p')
--version=VERSION, -v VERSION
product version
--component=COMPONENT, -c COMPONENT
component name(s), comma-separated (list with 'bugzilla info -c
PRODUCT')
--components_file=COMPONENTS_FILE
list of component names from a file, one component per line
(list with 'bugzilla info -c PRODUCT')
--long_desc=LONG_DESC, -l LONG_DESC
search inside bug comments
--target_milestone=TARGET_MILESTONE, -m TARGET_MILESTONE
search for a target milestone
--short_desc=SHORT_DESC, -s SHORT_DESC
search bug summaries
--bug_status=BUG_STATUS, -t BUG_STATUS
comma-separated list of bug statuses to accept [Default:all]
[Available:NEW,ASSIGNED,NEEDINFO,ON_DEV,MODI‐
FIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERI‐
FIED,RELEASE_PENDING,CLOSED]
--bug_severity=BUG_SEVERITY, --severity=BUG_SEVERITY, -x BUG_SEVERITY
search severities, comma-separated
--priority=PRIORITY, -z PRIORITY
search priorities, comma-separated
--emailtype=EMAILTYPE, -E EMAILTYPE
Email: specify searching option for emails, ie. substring,not‐
substring,exact,... [Default: substring]
--cc=CC, -o CC
Email: search cc lists for given address
--reporter=REPORTER, -r REPORTER
Email: search reporter email for given address
--assigned_to=ASSIGNED_TO, -a ASSIGNED_TO
Email: search for bugs assigned to this address
--qa_contact=QA_CONTACT, -q QA_CONTACT
Email: search for bugs which have QA Contact assigned to this
address
--url=URL, -u URL
search keywords field for given url
--url_type=URL_TYPE, -U URL_TYPE
specify searching option for urls, ie. anywords,allwords,nowords
--keywords=KEYWORDS, -k KEYWORDS
search keywords field for specified words
--keywords_type=KEYWORDS_TYPE, -K KEYWORDS_TYPE
specify searching option for keywords, ie. anywords,all‐
words,nowords
--status_whiteboard=STATUS_WHITEBOARD, -w STATUS_WHITEBOARD
search Status Whiteboard field for specified words
--status_whiteboard_type=STATUS_WHITEBOARD_TYPE, -W STATUS_WHITE‐
BOARD_TYPE
specify searching option for Status Whiteboard, ie. any‐
words,allwords,nowords
--booleantype=BOOLEANTYPE, -B BOOLEANTYPE
specify searching option for booleans, ie. substring,notsub‐
string,exact,... [Default: substring]
--boolean_query=BOOLEAN_QUERY
Boolean:Create your own query. Format: BooleanName-Condition-
Parameter &/| ... . ie, keywords-substring-Partner & keywords-
notsubstring-OtherQA
--blocked=BLOCKED
Boolean:search for bugs that block this bug ID
--dependson=DEPENDSON
Boolean:search for bugs that depend on this bug ID
--flag=FLAG
Boolean:search for bugs that have certain flag states present
--qa_whiteboard=QA_WHITEBOARD
Boolean:search for bugs that have certain QA Whiteboard text
present
--devel_whiteboard=DEVEL_WHITEBOARD
Boolean:search for bugs that have certain Devel Whiteboard text
present
--alias=ALIAS
Boolean:search for bugs that have the provided alias
--fixed_in=FIXED_IN
search Status Whiteboard field for specified words
--from-url=FROM_URL
Use the query given by a query.cgi URL. (Use quotes!)
--full, -f
output detailed bug info
--ids, -i
output only bug IDs
--extra, -e
output additional bug information (keywords, Whiteboards, etc.)
--oneline
one line summary of the bug (useful for scripts)
--raw raw output of the bugzilla contents
--outputformat=OUTPUTFORMAT
Print output in the form given. You can use RPM-style tags that
match bug fields, e.g.: '%{bug_id}: %{short_desc}'
‘MODIFY’ OPTIONS
--comment=COMMENT, -l COMMENT
Add a comment
--close=RESOLUTION, -k RESOLUTION
Close with the given resolution
--private, -p
Mark as private
--status=STATUS, -s STATUS
Change status of bug
--assignee=ASSIGNEE
Assign bugzilla to assignee
--qa_contact=QA_CONTACT
Change QA contact
--flag=FLAG, -f FLAG
Update bugzilla flags with requested type, ie fedora-cvs? (Use a
new option for each flag)
--cc=CC
Add an email to the cc list
--fixed_in=VERSION, -F VERSION
"Fixed in version" field
‘ATTACH’ OPTIONS
--file=FILENAME, -f FILENAME
File to attach, or filename for data provided on stdin
--description=DESCRIPTION, -d DESCRIPTION
A short description of the file being attached
--type=MIMETYPE, -t MIMETYPE
Mime-type for the file being attached
--get=ATTACHID, -g ATTACHID
Download the attachment with the given ID
--getall=BUGID, --get-all=BUGID
Download all attachments on the given bug
‘INFO’ OPTIONS
--products, -p
Get a list of products
--components=PRODUCT, -c PRODUCT
List the components in the given product
--component_owners=PRODUCT, -o PRODUCT
List components (and their owners)
--versions=PRODUCT, -v PRODUCT
List the versions for the given product
EXAMPLESbugzilla query --bug_id 62037
bugzilla query --version 15 --component python-bugzilla
bugzilla login
bugzilla create -p Fedora -v rawhide -c python-bugzilla \
--summary "python-bugzilla causes headaches" \
--comment "python-bugzilla made my brain hurt when I used it."
bugzilla attach --file ~/Pictures/cam1.jpg --desc "me, in pain" $BUGID
bugzilla attach --getall $BUGID
bugzilla modify --close NOTABUG --comment "Actually, you're hungover."
$BUGID
EXIT STATUSbugzilla normally returns 0 if the requested command was successful.
Otherwise, exit status is 1 if bugzilla is interrupted by the user (or
a login attempt fails), 2 if a socket error occurs (e.g. TCP connection
timeout), and 3 if the server returns an XML-RPC fault.
NOTES
Not everything that's exposed in the Web UI is exposed by XML-RPC, and
not everything that's exposed by XML-RPC is used by bugzilla.
BUGS
Bugs? In a sub-1.0 release? Preposterous.
AUTHOR
Will Woods <wwoods@redhat.com>
version 0.7.0 June 06, 2012 bugzilla(1)
