Sources
Research and Industry Evidence Ledger
Clickable list with the exact origin of each quantitative point used across the site.
This website combines peer-reviewed studies, preprints, project pages, and industry materials. Peer-reviewed findings are treated as highest confidence. Project and industry sources are labeled and used as practical context.
| Source | Authors | Venue / Year | Key finding used | Type | Link |
|---|---|---|---|---|---|
| What Makes a Good Bug Report? | Nicolas Bettenburg, Sascha Just, Adrian Schröter et al. | FSE / technical report, 2008 | Developers report a recurring information gap: missing steps to reproduce, stack traces, test cases, environment data. | peer-reviewed paper | https://www.st.cs.uni-saarland.de/publications/details/bettenburg-tr-2008/ |
| Information Needs in Bug Reports: Improving Cooperation Between Developers and Users | Silvia Breu, Rahul Premraj, Jonathan Sillito, Thomas Zimmermann | CSCW, 2010 | Sampled 600 bug reports and documented early-stage clarification questions in bug handling workflows. | peer-reviewed paper | https://thomas-zimmermann.com/publications/files/breu-cscw-2010.pdf |
| Deep Learning Based Valid Bug Reports Determination and Automated Bug Triage | J. He et al. | ISSRE, 2020 | Large-scale study and model for classifying valid/invalid reports using text-only features. | peer-reviewed paper | https://doi.org/10.1109/ISSRE5003.2020.00026 |
| Who Should Fix This Bug? | John Anvik, Lyndon Hiew, Gail C. Murphy | ICSE, 2006 | Triaging baseline of about 5 minutes per report was used to benchmark triage workload. | peer-reviewed paper | https://dl.acm.org/doi/10.1145/1134285.1134336 |
| Revisiting the Performance of Automated Approaches for the Retrieval of Duplicate Issue Reports | Rakha et al. | EMSE, 2017 | Reported duplicate prevalence in literature ranges that motivate 20–30% baseline duplicate burden. | peer-reviewed paper | https://researchr.org/publication/RakhaBH18 |
| An Empirical Study of Bug Fixing Rate | Weiqin Zou, Xin Xia et al. | COMPSAC, 2015 | Mozilla and Eclipse fixed/non-fixed outcomes used as non-fixed quality indicators. | peer-reviewed paper | https://research.monash.edu/en/publications/an-empirical-study-of-bug-fixing-rate/ |
| Feedback-Driven Automated Whole Bug Report Reproduction for Android Apps | X. Zhang et al. | ISSTA, 2024 | 90.63% success, 74.98 sec/report in benchmark. | peer-reviewed paper | https://arxiv.org/abs/2407.05165 |
| Prompting Is All You Need: Automated Android Bug Replay with Large Language Models | Authors listed in arXiv submission | arXiv, 2024 | 81.3% success with 253.6 sec/report. | peer-reviewed paper | https://arxiv.org/abs/2306.01987 |
| BugCraft: End-to-End Crash Bug Reproduction Using LLM Agents in Minecraft | Eray Yapıcı et al. | ASE, 2025 | Manual crash reproduction baseline of 3.41 days was reduced to minutes in several agent-comparison cases. | peer-reviewed paper | https://arxiv.org/abs/2503.20036 |
| Enhancing Mobile App Bug Reporting via Real-Time Understanding of Reproduction Steps | Mattia Fazzini, Kevin Moran, Carlos Bernal Cardenas et al. | IEEE Transactions on Software Engineering, 2022 | Report authors claim reporters built reports ~31% faster with guided S2R capture and higher reproducibility quality. | preprint | https://arxiv.org/abs/2203.12093 |
| Automated Generation of High-Quality Bug Reports for Android Applications | BugScribe authors | arXiv preprint, 2026 | 44.1%–82.3% relative improvement in S2R completeness and 3.8%–35.2% improvement in observed/expected behavior quality. | preprint | https://arxiv.org/abs/2604.01148 |
| Automated Duplicate Bug Reports Detection | Kang Li | DiVA thesis/industrial experiment, 2017 | Industrial experiment context reported estimated value around 2.8 hours per duplicate and 39,019 total projected hours in the referenced dataset context. | preprint | https://bth.diva-portal.org/smash/record.jsf?pid=diva2%3A1153748 |
| BugScribe project page | BugScribe Team | Project page, 2026 | Project materials report a manual writing drop from roughly 20 minutes to under 2 minutes. | project page Scenario assumption context included | https://bug-scribe.github.io/ |
| Adopting Automated Bug Assignment in Practice: A Longitudinal Case Study at Ericsson | Markus Borg, Leif Jonsson, Emelie Engström et al. | IEEE/Empirical Software Engineering, 2024 | Reported industrial adoption context with automation-driven assignment, including speedups and assignment accuracy context. | industry report | https://arxiv.org/abs/2209.08955 |
| The QA-Developer Handoff: Why 35% of Sprint Time Is Wasted | SnagRelay article authors | industry article, 2026 | 35% sprint-time waste claim and follow-up rate drop from >60% to under 10%. | industry report | https://snagrelay.com/ |
| What Is Support Cost per Ticket in SaaS? | Industry benchmarking source | industry benchmark, 2025 | Average support ticket cost used as operational planning benchmark, $15.56 in provided findings. | industry report Scenario assumption context included | https://www.which-50.com/support-cost-per-ticket-statistics/ |
| Bug Report Optimization: Creating Reports That Get Fixed Faster | Industry authors | industry article, 2025 | Reported benchmarked closure from 13 days to 4 days with higher report quality. | industry report | https://fullscale.io/blog/bug-report-optimization-distributed-teams/ |
| The Hidden Tax of Incomplete Bug Reports | QAFlow case study authors | industry case study, 2026 | 18–22 hours/week clarifications; 2.7 back-and-forth rounds; 8–12 hours delay per round. | industry case study | https://www.qaflow.com/ |