Root > Integral parts > Send engines > FogBugz


Previous pageReturn to chapter overviewNext page   

This send method creates a new issue on FogBugz bug tracker (see demo).


A bug tracking system is a software application that is designed to help quality assurance and programmers keep track of reported software bugs in their work. It may be regarded as a type of issue tracking system.


Many bug-tracking systems, such as those used by most open source software projects, allow users to enter bug reports directly. Other systems are used only internally in a company or organization doing software development. Typically bug tracking systems are integrated with other software project management applications.


Having a bug tracking system is extremely valuable in software development, and they are used extensively by companies developing software products. Consistent use of a bug or issue tracking system is considered one of the "hallmarks of a good software team".


This method requires some preparation actions, before you can use it:

1. You need to get web server with ASP.NET and database running or have a hosting with ASP.NET and database support. You can get it with FogBugz, if you buy FogBugz as service.
2. (Optional) You need to download FogBugz and upload it on web-server (either hosting or self-server). This step is optional, if you use FogBugz hosting services.
3. (Optional) You need to run through FogBugz installer. This step is optional, if you use FogBugz hosting services.


Important note: EurekaLog uses FogBugz XML API to access FogBugz. BugzScout is not used by EurekaLog with "FogBugz" send method, however you can use BugzScout with HTTP send method.


4. You need to setup FogBugz:
create projects (for each of your products).
create "reporter" account (warning: don't use administrator account for reporting issues).
5. Fill FogBugz details in your EurekaLog-enabled application.


You also need to setup sending options and test sending. To test send - place a button, which raises exception. Let EurekaLog handle it and perform sending. Ensure that it's working as expected. Send report again to check how duplicates are handled. Adjust any options, if needed. Change status of issue to "closed" and retry sending. Ensure that it works as expected.




Powerfull and customizable.
Bug report management.
Can be get as paid service with 0 setup time.
SSL/TLS support.
Easy to use.
Have a ready to use HTML facade: web-form and BugzScout.



Paid software.
May be blocked by firewall.
Requires setup.
Requires hosting OR web (http) server + database service.
User e-mail address is optional.
Requires setup for each your project.
Setup options and access rights may be not detailed enough.


Note: you may consider using HTTP upload method for FogBugz instead of using FogBugz API. See FogBugz setup for more detailed description; see FogBugz: using HTTP upload for detailed manual on HTTP Upload setup for FogBugz.


Constant: wsmFogBugz.



See also:


Send feedback... Build date: 2022-03-28
Last edited: 2021-04-14
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: