BugZilla send method options
1. "URL" (.SendBugZillaURL) option specifies target URL for your BugZilla installation. Do not add here "http://" or ":80" parts here. Specify only domain name (or IP) and path. Example: www.example.com/bugzilla/
Warning: be sure to setup adequate maximum upload file limits in your web-server/BugZilla configuration. Otherwise sending may fail on large bug reports.
2. "Port" (.SendBugZillaPort) option specifies HTTP port on web server. It's 80 by default. Other common value is 8080. For SSL/TLS it's usually 443. Port will be set automatically to 80/443 by default.
3. "SSL / TLS" (.SendBugZillaSSL) option enabled secure mode (HTTPS protocol). Port will be set automatically to 80/443 by default. Don't forget to adjust port number, if you are using an alternative port number.
4. "Login" (.SendBugZillaLogin) and "Password" (.SendBugZillaPassword) options specify your account on BugZilla server. This account will be used to submit bug reports. You can use API token instead of password - leave login field blank in this case.
Warning: your real account's data will be stored inside application. Even if it's encrypted - it's still stored inside .exe, so it can be stolen. DO NOT use BugZilla admin account here. Create a new special account for bug reporting via this method. Limit its rights to submitting only.
Note: it is a good idea to disable e-mail notifications for this account.
5. "BasicAuth" (.SendBugZillaBasicAuthLogin, .SendBugZillaBasicAuthPassword) options specify account details for Basic-Auth type authentication. Usually these fields are blank. Fill them, if you use Basic-Auth on your web server.
6. "Proxy" (.SendBugZillaProxyHost, .SendBugZillaProxyPort, .SendBugZillaProxyLogin, .SendBugZillaProxyPassword) options specify proxy details. You can leave them blank to use system-provided settings. Or you can fill these values to set custom proxy.
7. "Connect" button will try to connect to your BugZilla server using the specified URL/port/credentials. If you made a mistake in your configuration - an error message will be displayed. In case of success - field below will be populated from configuration of your bug tracker.
8. "Project" (.SendBugZillaProject) options specifies project name to store bug reports. It's mandatory.
9. "Assign to" (.SendBugZillaOwner) option specifies owner account name. If this option is empty, all submitted bug reports will be assigned to default account (configured in BugZilla options). If you enter here any account name - all submitted bug reports will be assigned to this account.
Note: this option is ignored, if submitted bug report already exists (submitting a known issue).
10. "Component" (.SendBugZillaComponent) option specifies category for submitted reports. It can be optional or mandatory - it depends on your BugZilla version and project configuration.
11. ""Count" field name" (.SendBugZillaCountFieldName) option specifies name of custom field, which EurekaLog will use for bug report counting. By default, BugZilla doesn't have any "occurrences" or "count" fields, so you can't know how many times bug has occurred. To workaround this problem, you can create a custom field in BugZilla configuration, which you will use for this purpose. You can enter name of this field here - and EurekaLog will use it to count bugs.
Note: we highly recommend to create and use this field.
See also: issues workflow.
12. ""E-mail" field name" (.SendBugZillaEMailFieldName) option specifies name of custom field, which EurekaLog will use to store e-mail of user who sent (original) report. By default, BugZilla doesn't have such field. You can either create a custom field in BugZilla configuration, which you will use for this purpose; or you can simply extract e-mail from bug report (file attach).
13. ""BugID" field name" (.SendBugZillaBugIDFieldName) option specifies name of custom field, which EurekaLog will use to store BugID. By default, BugZilla doesn't have such field. You can create a custom field in BugZilla configuration, which you will use for this purpose. It is purely optional, as EurekaLog will use internal alias for merging.
14. "In progress statuses" (.SendBugZillaInProgressStatuses) option specifies which statuses indicate that issue is IN PROGRESS. The list can contain one of more values. Separate individual values with semicolon (";"). This option is case insensitive.
See also: issues workflow.
15. "Use/fill "Hardware" field" (.SendBugZillaUseHardware) option instructs EurekaLog to use "Hardware" field in BugZilla. Disable this option, if you've customized this field and/or use it for other purposes. You can also fill this field manually instead of automatic generation by EurekaLog.
16. "Use/fill "OS" field" (.SendBugZillaUseOS) option instructs EurekaLog to use "OS" field in BugZilla. Disable this option, if you've customized this field and/or use it for other purposes. You can also fill this field manually instead of automatic generation by EurekaLog.
17. "Use/fill "Version" field" (.SendBugZillaUseVersion) option instructs EurekaLog to use "Version" field in BugZilla. Disable this option, if you've customized this field and/or use it for other purposes. You can also fill this field manually instead of automatic generation by EurekaLog.
18. "Search match up to N numbers" (.SendBugZillaMinVersion) option specifies how version search is performed.
Because bug tracker may create versions in an arbitrary format (like "Version 1" or "7.3 hotfix 2"), and application uses 4 numbers format (like "220.127.116.11") - EurekaLog has to perform heuristic search:
This option indicate when EurekaLog need to stop when searching version:
We recommend to use value of 4 for this option, because it greatly reduces possible ambiguity. However, it will mean that you have to enter each build (even very minor one) of your application in your bug tracker's configuration.
Value of 1 means using very wide criteria. We do not recommend to use it. If you are still going to use it - be sure not to enter too much sub-versions in your bug tracker, especially with added text.
Values of 2 and 3 are a good compromise.
We highly do not recommend to use value of 0.
19. "Upload bug report files for duplicates until bug is closed" (.SendBugZillaUploadFilesForDups) option allows you to collect all bug reports. If this option is unchecked (default): only first bug report is uploaded and stored. All other bug reports for the same problem (identified by BugID) will be discarded. Only "count" field will be increased (if it was configured). If this option is checked: bug reports for the same problem will be uploaded to issue.
See also: issues workflow.
20. "Append bug report text to additional information" (.SendBugZillaAppendText) option allows you to insert bug report's text into "Description" field. It's convenient, if you need to peek bug report without downloading bug report file. You can turn this option off, if you don't need this behaviour.
Note: checking this option will not disable bug report file upload. File will still be attached.
21. "Append only call stack instead of full report" (.SendBugZillaUseCallStackAsBugReport) option alters previous option. Disabled: full bug report text will be added (e.g. general section, call stack, modules, processes, CPU/assembler, etc.); Enabled: only call stack will be added (you will still be able to view full bug report by downloading file attach).
22. "Append bug opening link to "Success" message" (.SendBugZillaAllowLinks) option will add a link to view bug report on BugZilla to message dialog after successful send. So end user (client) will be able to view status of the report on your bug tracker (login is required).
This option has no effect if successful message dialog is disabled. Turn this option on for public bug trackers. Turn this option off for private bug trackers.
"Append bug opening link to "Success" message" option is enabled
"Append bug opening link to "Success" message" option is disabled
Note: active hyper-link will work on Windows Vista or later. It will be displayed as plain text on Windows XP and earlier.