Automated Root-Cause Subclassification and No-Code Fix Generation for Invalid Bug Reports
Not on the map. Why?
Abstract (arXiv)
Issues faced when using software are reported in the form of bug reports. However, many bug reports are invalid, meaning they do not require code changes, and are resolved with a no-code fix. Manually determining the root cause of the invalid bug reports and providing actionable resolutions by the customer support causes a serious waste of resources. Our goal is to introduce a standardized taxonomy for root-cause oriented invalid bug report subclassification, and perform experiments to test the accuracy of various approaches on invalid subclassification and no-code fix generation. We study how different configurations perform on a gold-standard benchmark we have created. Using a manually curated benchmark for higher quality analysis, we experimented with vanilla LLMs, Retrieval Augmented Generation, and agentic web search to identify invalid subclasses and generate no-code fixes. We evaluated the results against manually labeled ground truth data that includes the invalid subclass and no-code fixes from the original bug reports. We measured subclass detection performance with weighted F1-Score, and assessed no-code fix suggestions using BERTScore and Judge LLM success rates. For subclassification, retrieval augmented generation achieves the highest overall performance with 0.66 weighted F1, slightly outperforming vanilla LLMs at 0.65 and agentic web search at 0.64. At the subclass level, performance peaks at 0.85 F1 for Non-reproducibility and 0.79 for Feature Request and Question, while Wrong Version remains the most challenging with scores between 0.00 and 0.29. For no-code fix generation, agentic web search achieves the highest overall Judge LLM success rate at 68.9%, compared to 64.4% for RAG applications and 64.9% for vanilla LLMs, with subclass-level peaks of 87.4% for Working as Designed and 72.2% for Question.
Key facts. Cited by 1 paper in the map (data through 7 Oct 2026). Builds on 23 of its 72 references that are in the map. First posted on arXiv 17 May 2026.
Builds on
23 of 72 references.
References · 23
- 2019BERTScore: Evaluating Text Generation with BERTcited by 5,462
- 2023SWE-bench: Can Language Models Resolve Real-World GitHub Issues?cited by 3,193
- 2024LiveCodeBench: Holistic and Contamination Free Evaluation of Large Language Models for Codecited by 1,906
- 2026GLM-5: from Vibe Coding to Agentic Engineeringcited by 502
- 2026Kimi K2.5: Visual Agentic Intelligencecited by 449
- 2025WebThinker: Empowering Large Reasoning Models with Deep Research Capabilitycited by 320
- 2023How Language Model Hallucinations Can Snowballcited by 310
- 2024AutoCodeRover: Autonomous Program Improvementcited by 272
- 2025Why Language Models Hallucinatecited by 205
- 2025Agentic Reasoning: A Streamlined Framework for Enhancing LLM Reasoning with Agentic Toolscited by 106
- 2025WebExplorer: Explore and Evolve for Training Long-Horizon Web Agentscited by 86
- 2024SpecRover: Code Intent Extraction via LLMscited by 71
11 more
- 2025From Web Search towards Agentic Deep Research: Incentivizing Search with Reasoning Agentscited by 49
- 2025ECom-Bench: Can LLM Agent Resolve Real-World E-commerce Customer Support Issues?cited by 27
- 2025Retrieval-Augmented Code Generation: A Survey with Focus on Repository-Level Approachescited by 20
- 2025BrowseMaster: Towards Scalable Web Browsing via Tool-Augmented Programmatic Agent Paircited by 16
- 2025A Simple Ensemble Strategy for LLM Inference: Towards More Stable Text Classificationcited by 8
- 2019"Won't We Fix this Issue?" Qualitative Characterization and Automated Identification of Wontfix Issues on GitHubcited by 4
- 2025Past, Present, and Future of Bug Tracking in the Generative AI Eracited by 4
- 2025GitBugs: Bug Reports for Duplicate Detection, Retrieval Augmented Generation, Triage, and Morecited by 3
- 2025RAG4Tickets: AI-Powered Ticket Resolution via Retrieval-Augmented Generation on JIRA and GitHub Datacited by 2
- 2026ImproBR: Bug Report Improver Using LLMscited by 2
- 2025Automated Bug Triaging using Instruction-Tuned Large Language Modelscited by 1
Built on by
Citing papers per year: 2026: 1.
1 paper.
Similar, not cited
Close in wording, no citation either way
- 2025From Reviewers' Lens: Understanding Bug Bounty Report Invalid Reasons with LLMs
- 2026Characterizing and Mitigating False-Positive Bug Reports in the Linux Kernel
- 2026Active-SWE: Benchmarking Coding Agents for Proactive Bug Fixing without Issue Reports
- 2025LLM-Based Detection of Tangled Code Changes for Higher-Quality Method-Level Bug Datasets
- 2025Self-Bootstrapping Automated Program Repair: Using LLMs to Generate and Evaluate Synthetic Training Data for Bug Repair
- 2025Abstain and Validate: A Dual-LLM Policy for Reducing Noise in Agentic Program Repair
- 2025Agentic Bug Reproduction for Effective Automated Program Repair at Google
- 2025From Bugs to Benchmarks: A Comprehensive Survey of Software Defect Datasets ↗