Casimiro Conde Marco Neto
ABSTRACT
Issue tracking systems help software development teams in identifying problems to be solved and new features to be added to a software system. In this paper, we replicate and extend a study carried out in 2013 on the usage of the issue tracking system provided by the GitHub platform. The replication aims at determining whether the results observed four years ago are still valid. The extension seeks to analyze how often issues are terminated by commits to the version control system and understand whether this feature allows developers to relate an issue to the source code modules that were changed to resolve it. We conclude that the results of the previous study remain valid and that issues closed by commits are uncommon (about 4% of our sample) and often linked to technical aspects of the project.
Supplemental Material
Available for Download
Supplemental material.
- T.F. Bissyande, D. Lo, J.Lingxiao, L. Reveillere, and Y. Le Traon. 2013. Got Issues? Who Cares About It? A Large Scale Investigation of Issue Trackers from GitHub. In IEEE 24th Intl Symposium on Software Reliability Engineering. 188--197.Google Scholar
- J. Cabot, J.L.C. Izquierdo, and V. Cosentino. 2015. Exploring the Use of Labels to Categorize Issues in Open-Source Software Projects. In Software Analysis, Evolution and Re engineering (SANER'15). 550--554.Google Scholar
- J. Cohen. 1992. A Power Primer. Psychological Bulletin (1992), 155--159.Google Scholar
- L. Dabbish, C. Stuart, J. Tasy, and J. Herbsleb. 2012. Social Coding in GitHub: Transparency and Collaboration in an Open Software Repository. In ACM 2012 Conference on Computer Supported Cooperative Work. 1277--1286. Google ScholarDigital Library
- E. Kalliamvakou, K. Blincoe, L. Singer, and D. Damian. 2014. The Promises and Perils of Mining GitHub. In 11th Working Conference on Minig Software Repositories (MSR'14). 92--101. Google ScholarDigital Library
- M.J. Lee, B. Ferwerda, J. Choi, J. Hahn, J. Moon, and J. Kim. 2013. GitHub developers use rockstars to overcome overflow of News. In Human Factors in Computing System. 233. Google ScholarDigital Library
- Y. Weicheng, S. Beijun, and X. Ben. 2013. Mining GitHub: Why commit stops - Exploring the relationship between developer's commit pattern and file version evolution. In Proc. of the Asia-Pacific Software Engineering Conference. 165--169.Google Scholar
- J. Xavier, A. Macedo, and M. A. Maia. 2014. Understanding the popularity of reporters and assignees in the Github. In 26th International Conference on Software Engineering and Knowledge Engineering. 484--489.Google Scholar
- E. Yong. 2012. Bad Copy. Nature 495 (2012), 298--300.Google ScholarCross Ref
Index Terms
- A structured survey on the usage of the issue tracking system provided by the GitHub platform
Recommendations
Do visual issue reports help developers fix bugs?: a preliminary study of using videos and images to report issues on GitHub
ICPC '22: Proceedings of the 30th IEEE/ACM International Conference on Program ComprehensionIssue reports are a pivotal interface between developers and users for receiving information about bugs in their products. In practice, issue reports often have incorrect information or insufficient information to enable bugs to be reproduced, and this ...
An Exploratory Study on Architectural Knowledge in Issue Tracking Systems
Software ArchitectureAbstractSoftware developers use issue trackers (e.g. Jira) to manage defects, bugs, tasks, change requests, etc. In this paper we explore (a) how architectural knowledge concepts (e.g. architectural component behavior, contextual constraints) are ...
“Won’t We Fix this Issue?” Qualitative characterization and automated identification of wontfix issues on GitHub
Abstract Context: Addressing user requests in the form of bug reports and Github issues represents a crucial task of any successful software project. However, user-submitted issue reports tend to widely differ in their quality, and ...
Comments