Root > Solving bugs in your code > Managing bug reports in issue tracker > Using unsupported bug tracker software

Using unsupported bug tracker software

Previous pageReturn to chapter overviewNext page   

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.



E-mail delivery

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:

1. Create new e-mail account for bug reports collection.
2. Setup your bug tracker software to pick up e-mail from that account (please, refer to documentation of your bug tracker software).
3. Setup e-mail delivery in your EurekaLog-enabled application.


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.

Mantis (external plugin)
GitLab (or you can use Service Desk)


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



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).


You can:

1. Enable anonymous reporting - which makes this web-form accessible.
2. Study this page source to retrieve names of expected fields and possible values.
3. Once you figure out required information:
setup HTTP upload method in EurekaLog
add OnCustomWebField event handler to supply fields and values as required by web-form


There are few examples available here and here. Additionally, GitLab allows you to use Jira as bug tracker for project's issues. And Jira allows you to use issue collectors.


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


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:

no end-user feedback: you may not be able to report back status of bug ticket to end client (like "closed"/"resolved"/"opened") - see also customizing feedback
no file attaches: you may be not able to attach bug report files (i.e. use only text messages)
no duplication management: each bug report may create new ticket in your bug tracker software
no user management: reports most likely are anonymous


These limitations are examples. It's not necessary that you'll encounter them. It depends on your bug tracker software and its features.



Manual Solution

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.



See also:

Send feedback... Build date: 2023-09-11
Last edited: 2023-03-07
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: