EurekaLog uses BugID to identify exceptions and leaks. BugID is a hash of exception information. Two exceptions with the same BugID are considered to be the same.
EurekaLog uses BugID to determinate if the current exception was already reported or not:
|•||If BugID of current exception is not found in bug tracker (e.g. current exception is not reported yet) - EurekaLog will create a new issue in bug tracker, set "count" field to 1, attach a bug report;|
|•||If BugID of current exception is found in bug tracker (e.g. current exception is already reported) - EurekaLog will not create new issue. The exact behavior depends on status of the issue in bug tracker.|
EurekaLog supports three stages (statuses) for bugs in a bug tracker:
Supported issue workflow in a bug tracker
|•||NEW. This is a default status. New (freshly posted) issues will have this status. The issue is opened. The "count" field will be updated. The bug report file attaches will be added. This state is used to collect information and reports about issue. Typical status names are: "new", "open", "reopened", "feedback", etc.|
|•||IN PROGRESS. This is the status that may be manually assigned to NEW issue. It indicates that issue is confirmed, reproduced, and developers are working on it. The "count" field is still updated, but new bug reports will be rejected. This state indicate that developer do not need any more information on the issue. This status is used mostly to stop accepting bug reports for popular issues. It is not necessary to put issues to this state, you can simply close / resolve issue instead. Typically, status names can be anything, except statuses for NEW and statuses for CLOSED. Few examples: "in progress", "assigned", "confirmed", "accepted", "review", "blocked", "verified", "acknowledged", etc. FogBugz only: an issue can be put in this state by switching BugzScout issue to "Stop reports".|
|•||CLOSED. This is the status that must be manually assigned to NEW or IN PROGRESS issue. The issue is closed, e.g. resolved or rejected. The "count" field is not updated. The bug reports will be rejected. This state indicate that developer do not need any more information on the issue, and there is a solution for the issue. Additionally, this status is treated differently when sending report: see "Only "bug closed"-message" option, for example. Finally, this status allows customization via notes (comments) and special tags. Typical status names are: "closed", "resolved", "done", "fixed", "rejected", etc.|
If you are not satisfied with default workflow - you can customize it.
Build date: 2019-12-02
Last edited: 2019-06-12
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/bug_tracker_workflow.php