1REPORTER-BUGZILLA(1)           LIBREPORT MANUAL           REPORTER-BUGZILLA(1)
2
3
4

NAME

6       reporter-bugzilla - Reports problem to Bugzilla.
7

SYNOPSIS

9       reporter-bugzilla [-vbf] [-g GROUP]... [-c CONFFILE]... [-F FMTFILE]
10       [-A FMTFILE2] -d DIR
11
12       Or:
13
14       reporter-bugzilla [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE...
15
16       Or:
17
18       reporter-bugzilla [-v] [-c CONFFILE]... [-d DIR] -t[ID] -w
19
20       Or:
21
22       reporter-bugzilla [-v] [-c CONFFILE]... -h DUPHASH [-p[PRODUCT]]
23

DESCRIPTION

25       The tool reads problem directory DIR. Then it logs in to Bugzilla and
26       tries to find a bug with the same abrt_hash:HEXSTRING in Whiteboard.
27
28       If such bug is not found, then a new bug is created. Elements of DIR
29       are stored in the bug as part of bug description or as attachments,
30       depending on their type and size.
31
32       Otherwise, if such bug is found and it is marked as CLOSED DUPLICATE,
33       the tool follows the chain of duplicates until it finds a non-DUPLICATE
34       bug. The tool adds a new comment to found bug.
35
36       The URL to new or modified bug is printed to stdout and recorded in
37       reported_to element in DIR.
38
39       Option -t uploads FILEs to the already created bug on Bugzilla site.
40       The bug ID is retrieved from directory specified by -d DIR. If problem
41       data in DIR was never reported to Bugzilla, upload will fail.
42
43       Option -tID uploads FILEs to the bug with specified ID on Bugzilla
44       site. -d DIR is ignored.
45
46       Option -w adds bugzilla user to bug’s CC list.
47
48       Option -r sets the last url from reporter_to element which is prefixed
49       with TRACKER_NAME to URL field. This option is applied only when a new
50       bug is to be filed. The default value is ABRT Server"
51
52   Configuration file
53       If not specified, CONFFILE defaults to
54       /etc/libreport/plugins/bugzilla.conf and to user’s local
55       ~/.config/libreport/bugzilla.conf. Configuration file lines should have
56       PARAM = VALUE format. The parameters are: User’s local configuration
57       overrides the system wide configuration.
58
59       Login
60           Login to Bugzilla account.
61
62       Password
63           Password to Bugzilla account.
64
65       BugzillaURL
66           Bugzilla HTTP(S) address. (default: https://bugzilla.redhat.com)
67
68       SSLVerify
69           Use yes/true/on/1 to verify server’s SSL certificate. (default:
70           yes)
71
72       Product
73           Product bug field value. Useful if you needed different product
74           than specified in /etc/os-release
75
76       ProductVersion
77           Version bug field value. Useful if you needed different product
78           version than specified in /etc/os-release
79
80       Parameters can be overridden via $Bugzilla_PARAM environment variables.
81
82   Formatting configuration files
83       Lines starting with # are ignored.
84
85       Lines can be continued on the next line using trailing backslash.
86
87       Format:
88
89       "%summary
90           summary format"
91
92       "section
93           element1[,element2]..." The literal text line to be added to
94           Bugzilla comment. Can be empty. (Empty lines are NOT ignored!)
95
96               Summary format is a line of text, where %element% is replaced by
97               text element's content, and [[...%element%...]] block is used only if
98               %element% exists. [[...]] blocks can nest.
99
100               Sections can be:
101               - %summary: bug summary format string.
102               - %attach: a list of elements to attach.
103               - text, double colon (::) and the list of comma-separated elements.
104
105               Elements can be:
106               - problem directory element names, which get formatted as
107                 <element_name>: <contents>
108                 or
109                 <element_name>:
110                 :<contents>
111                 :<contents>
112                 :<contents>
113               - problem directory element names prefixed by "%bare_",
114                 which is formatted as-is, without "<element_name>:" and colons
115               - %oneline, %multiline, %text wildcards, which select all corresponding
116                 elements for output or attachment
117               - %binary wildcard, valid only for %attach section, instructs to attach
118                 binary elements
119               - problem directory element names prefixed by "-",
120                 which excludes given element from all wildcards
121
122               Nonexistent elements are silently ignored.
123               If none of elements exists, the section will not be created.
124
125   Integration with ABRT events
126       reporter-bugzilla can be used as an ABRT reporter. Example fragment for
127       /etc/libreport/report_event.conf:
128
129           # Report Python crashes
130           EVENT=report_Bugzilla analyzer=Python
131                 reporter-bugzilla -d . -c /etc/libreport/plugins/bugzilla.conf
132

OPTIONS

134       -d DIR
135           Path to problem directory.
136
137       -c CONFFILE
138           Path to configuration file.
139
140       -b
141           When creating bug, attach binary files too.
142
143       -f
144           Force reporting even if this problem is already reported.
145
146       -F CONF_FORMAT_FILE
147           Formatting file for initial comment. Default:
148           /etc/libreport/plugins/bugzilla_format.conf
149
150       -A CONF_FORMAT_FILE
151           Formatting file for duplicates. Default:
152           /etc/libreport/plugins/bugzilla_format.conf
153
154       -t[ID]
155           Upload FILEs to the already created bug on Bugzilla site.
156
157       -w
158           Add bugzilla user to CC list [of bug with this ID]. Applicable only
159           with -t.
160
161       -h, --duphash DUPHASH
162           Search in Bugzilla by abrt’s DUPHASH and print BUG_ID.
163
164       -p[PRODUCT], --product[PRODUCT]
165           Specify a Bugzilla’s product (ignored without -h). Default:
166           "Fedora". If only -p or --product without PRODUCT is presented
167           either value from environment variable Bugzilla_Product in the
168           first place or REDHAT_BUGZILLA_PRODUCT value from /etc/os-release
169           is used.
170
171       -g, --group GROUP
172           When creating a new ticket restrict access to this group only.
173

ENVIRONMENT VARIABLES

175       Environment variables take precedence over values provided in the
176       configuration file.
177
178       Bugzilla_Login
179           Login to Bugzilla account.
180
181       Bugzilla_Password
182           Password to Bugzilla account.
183
184       Bugzilla_BugzillaURL
185           Bugzilla HTTP(S) address. (default: https://bugzilla.redhat.com)
186
187       Bugzilla_SSLVerify
188           Use yes/true/on/1 to verify server’s SSL certificate. (default:
189           yes)
190
191       Bugzilla_Product
192           Product bug field value. Useful if you needed different product
193           than specified in /etc/os-release
194
195       Bugzilla_ProductVersion
196           Version bug field value. Useful if you needed different product
197           version than specified in /etc/os-release
198
199       Bugzilla_PrivateGroups
200           List of Bugzilla group names that will be set to the new bug if
201           Bugzilla_CreatePrivate equals yes
202
203       Bugzilla_CreatePrivate
204           Use yes/no to control whether the new bug should have set groups
205           listed in Bugzilla_PrivateGroups
206
207       Bugzilla_DontMatchComponents
208           Comma-separated list of package components (e.g. selinux-policy,
209           anaconda) for which reporter-bugzilla should not use Bugzilla
210           component match when searching for duplicate bug reports.
211
212       http_proxy
213           the proxy server to use for HTTP
214
215       HTTPS_PROXY
216           the proxy server to use for HTTPS
217

FILES

219       /usr/share/libreport/conf.d/plugins/bugzilla.conf
220           Readonly default configuration files.
221
222       /etc/libreport/plugins/bugzilla.conf
223           Configuration file.
224
225       ~/.config/libreport/bugzilla.conf
226           User’s local configuration file.
227
228       /etc/libreport/plugins/bugzilla_format.conf
229           Configure formating for reporting.
230

SEE ALSO

232       report_event.conf(5), bugzilla_format.conf(5)
233

AUTHORS

235       •   ABRT team
236
237
238
239LIBREPORT 2.15.2                  07/22/2021              REPORTER-BUGZILLA(1)
Impressum