The bug-assignment problem is commonly stated as a method of evaluating developers according to their ability to fix a specific bug. Previous methods in the field used machine-learning or information-retrieval techniques and used textual aspects of bug reports as evidence of developer ability to assign a score to each developer and arrange the developers for each bug report. Despite the subject's relevance and the considerable attention it has received from researchers, it remains a difficult and time-consuming effort in major software projects. Even now, there is no consensus on how to validate and compare bug-assignment procedures, and many approaches documented in the literature are not repeatable.
Product | Free Trial | Starting Price | Spot Score | Rating | Actions |
---|---|---|---|---|---|
Sentry | - | 9.8 | 4.2 | Visit Website | |
Bugsnag | - | 9.7 | 4.4 | Visit Website | |
Instabug | - | 9.6 | 4.2 | Visit Website | |
TestRail | - | 9.6 | 4.4 | Visit Website | |
Usersnap | - | 9.4 | 4.5 | Visit Website | |
Airbrake | $29, | 9.2 | 4.5 | Visit Website | |
Userback | $14, Billed Yearly | 9.1 | 4.7 | Visit Website | |
Ubertesters | - | 9.1 | 4.5 | Visit Website | |
Backlog | $29.16, Billed Yearly | 9 | 4.3 | Visit Website | |
zipBoard | $39, Billed Yearly | 8.9 | - | Visit Website | |
Bugfender | - | 8.9 | 4.2 | Visit Website | |
AWS X-Ray | - | 8.8 | 4 | Visit Website | |
Zoho BugTracker | - | 8.8 | 4.4 | Visit Website | |
DoneDone | $4, Billed Yearly | 8.7 | 4.3 | Visit Website | |
MantisBT | - | 8.7 | 4 | Visit Website |