Root > Integral parts > Send engines > Jira/BitBucket


Previous pageReturn to chapter overviewNext page   

This send method creates a new issue on Jira bug tracker (see demo). This article refers to Jira bug tracker, which was initially known as "just Jira". Later it was renamed to "Jira Software". This article does not reference "Jira Core", "Jira Service Management", "Jira Service Desk", "Jira Align", "Jira Work Management" or any other product from Atlassian Jira family. Jira bug tracker can be integrated with BitBucket. If you are looking for a way to submit bug reports to Jira Service Desk instead ("Jira Service Management") - you can use Jira issue collectors.


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


Jira Software is defined by its maker, Atlassian, as "part of a family of products designed to help teams of all types manage work." The software maker says that the product was made initially for issue and bug tracking. Over the years, Atlassian has developed Jira into what it calls a powerful workflow management tool for different kinds of use cases, including quality assurance tasks like defect tracking. There are a lot of different products that can be integrated with Jira. For example: 10 Best Test Management Tools For Jira. You can also browse marketplace for a full list.


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

1. You need to get server with JAVA installed (Windows/Linux/Solaris only) and database running or have a hosting with similar requirements.
2. (Optional) You need to download Jira and upload it on server (either hosting or self-server). This step is optional, if you use Jira hosting services.
3. (Optional) You need to run through Jira installer. This step is optional, if you use Jira hosting services.


Important note: EurekaLog uses JSON API to access Jira. Make sure you have enabled remote access via API in Jira options. Please refer to Jira documentation for more information.


4. You need to setup Jira:
create projects (for each of your products).
create "reporter" account (warning: don't use administrator account for reporting issues).
create custom field for "counting" bug reports.
5. Fill Jira 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.
Setup options are easy to use.
Cheap or free for personal use/small teams/evaluation.
Have a ready to use HTML facade: Issue Collector.
Rich ecosystem offers A LOT of integrations with various software



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.


Constant: wsmJira.



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: