Decoding the Issue Resolution Process in Practice via Issue Report Analysis: A Case Study of Firefox
Antu Saha, Oscar Chaparro

TL;DR
This study investigates how Mozilla Firefox developers manage issue resolution by analyzing 356 issue reports, revealing common process patterns and providing insights to improve software maintenance practices.
Contribution
It offers a detailed analysis of real-world issue resolution sequences in Firefox, identifying 47 process patterns and their implications for software engineering.
Findings
Identified 47 common issue resolution patterns.
Analyzed process complexity and resolution times.
Provided insights for improving issue management.
Abstract
Effectively managing and resolving software issues is critical for maintaining and evolving software systems. Development teams often rely on issue trackers and issue reports to track and manage the work needed during issue resolution, ranging from issue reproduction and analysis to solution design, implementation, verification, and deployment. Despite the issue resolution process being generally known in the software engineering community as a sequential list of activities, it is unknown how developers implement this process in practice and how they discuss it in issue reports. This paper aims to enhance our understanding of the issue resolution process implemented in practice by analyzing the issue reports of Mozilla Firefox. We qualitatively and quantitatively analyzed the discussions found in 356 Firefox issue reports, to identify the sequences of stages that developers go through…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsAcademic Publishing and Open Access · Big Data and Business Intelligence · FinTech, Crowdfunding, Digital Finance
