This send method creates a new issue on JIRA 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 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.|
|•||Can be get as paid service with 0 setup time.|
|•||Setup options are easy to use.|
|•||Cheap for personal use/small teams/evaluation.|
|•||May be blocked by firewall.|
|•||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.|
Build date: 2019-07-01
Last edited: 2019-01-30
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: https://www.eurekalog.com/help/eurekalog/jira.php