This article is part of Managing bug report in issue tracker series.
EurekaLog supports these send methods. However you may need to send your bug reports into another bug/issue tracking software which is not presented in the list of supported bug trackers. This doesn't mean that you can't use your bug tracker software with EurekaLog at all - you actually can.
First method to try is to use e-mail delivery. EurekaLog supports wide range of e-mail sending methods and you can choose one or several methods for delivery bug reports to you. Many bug tracker software includes feature of inserting incoming e-mail as tickets into bug tracker's database - either as integral feature or as 3rd party plugin.
Typically, you need:
Your bug tracker software may require e-mail messages to be in some predefined format - to avoid inserting spam e-mails into database. In this case you need to appropriately setup e-mail body in EurekaLog's project settings.
Here are examples of e-mail delivery features in bug trackers which are supported by EurekaLog.
Surely, usually you don't need to use these interfaces for the mentioned bug trackers - because EurekaLog has support for API of these bug trackers. But these links are examples only. It gives you an idea what to search in the documentation of your bug tracker. It serves as starting point for studying. Alternatively, you may use these links if you want to hide your bug tracker behind e-mail facade.
Search documentation of your bug tracker software for terms "incoming e-mails", "e-mail reporting", "e-mail reports", "e-mail cases", "customer e-mails", etc. You can also ask your bug tracker's support about existence of such feature. You can mention reference to this article, which is available online at https://www.eurekalog.com/help/eurekalog/unsupported_bug_tracker.php
Web-form HTTP posting
Another method to try is HTTP upload method. This method is like posting web-form. Some bug trackers allow anonymous bug reporting, which typically includes a web-page which anyone can use to report issues. Usually anonymous reporting is disabled by default (if it exists at all).
Search documentation of your bug tracker software for terms "anonymous reports", "anonymous cases", "anonymous users", "anonymous submitting", "web form", etc. You can also ask your bug tracker's support about existence of such feature. You can mention reference to this article, which is available online at https://www.eurekalog.com/help/eurekalog/unsupported_bug_tracker.php
Note: web-form posting is subject to dependence of UI changes. For example, if you're using web-access method - then you may need to use name like "Root project/Your project" to use project created as sub project; category can be specified as "[All Projects] General"; custom field in Mantis will be like "custom_field_1", "custom_field_2", etc.; custom fields in BugZilla have form like "cf_count", "cf_mail", etc. Again, you should look at the page's source to get these names.
Surely, work with unsupported bug tracker will be limited.
Here is the list of possible limitations:
These limitations are examples. It's not necessary that you'll encounter them. It depends on your bug tracker software and its features.
Finally, there is always an option of manual implementation for your bug tracker. Refer to documentation of your bug tracker to learn about its API. Refer to ESendAPIxyz.pas files to learn about reference implementation in EurekaLog. Implement API support in your bug tracker in a standalone unit (follow existing code for supported bug tracker as example). Configure your sending method at run-time.