View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022263 | mantisbt | api soap | public | 2017-01-26 13:35 | 2020-02-04 14:44 |
Reporter | GunSmoker | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | new | Resolution | open | ||
Product Version | 2.0.0 | ||||
Summary | 0022263: Mantis lacks features for automated crash reporting / "exception driven development" | ||||
Description | Software developers usually build exception and error reporting facility for their applications. Application should be able to automatically send bug reports for each crash. There must be a central place where all bug reports are collected (e.g. like Mantis), which may be used as TO-DO list for developers to fix bugs. The idea here is to merge reports about the same crash (from different users) into one bug on Mantis. The more crashes bug receives - the greater priority it will have. So you can fix, say, top 3 bugs in your list - and solve the majority of problems that your users are having. The problem is that Mantis is not suited for this kind of work. The problems are (*):
The suggestions are:
| ||||
Steps To Reproduce | (*) Obviosly, you can workaround Mantis problems by:
However, there are major problems with this workaround:
| ||||
Additional Information | https://blog.codinghorror.com/exception-driven-development/ - more about the described crash reporting idea http://help.fogcreek.com/the-fogbugz-api/bugzscout - a similar feature in Fogbugz bug tracker. Cases (bugs) about crashes are called "BugzScout cases". "Alias" is called "sScoutDescription", "count" is called "Occurrences". Scout cases can be send via usual fully-featured Fogbugz API or via dedicated "send-report-only" BugzScout API. http://help.fogcreek.com/7566/bugzscout-for-automatic-crash-reporting - description of BugzScount simplified API. Bugzilla also have "alias" / "bug-id" / "bug-hash" field (which is called - "alias"). JIRA has "votes" (e.g. "occurrences") and ability to search by most voted issues. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
It seems to be that you've described ABRT :-) Incidentally, ABRT has MantisBT integration so this should suit your needs. |
|
Honestly, Fogbuz suits my needs :) However, we historically use Mantis. |
|
Even if you look at ABRT: https://github.com/abrt/libreport/wiki/MantisBT - you will see that docs says it has problems, because Mantis lacks the mentioned features (unlike Bugzilla), so they have to use workarounds. |
|
Screenshots of working feature. |
|
This can also be integrated with 0022203 |
|
https://exceptionless.com/exceptionless-api-usage-and-overview/ - a similar feature in Exceptionless bug tracker. A scoped token allows access only for "post event" API. Additionally, posting event allows you to specify pre-made "reference id" (a custom ID to view bug report via web), as well as "ManualStackingKey" - for automatic merging same bug reports into one ticket with automatic increase of "Count" (e.g. same as above-discussed "alias", "bug-id", "sScoutDescription"), so you can view unique bug reports only. |
|