Got issues? Who cares about it? A large scale investigation of issue trackers from GitHub
Open accessThe DOI matches its Crossref record.
Abstract
Feedback from software users constitutes a vital part in the evolution of software projects. By filing issue reports, users help identify and fix bugs, document software code, and enhance the software via feature requests. Many studies have explored issue reports, proposed approaches to enable the submission of higher-quality reports, and presented techniques to sort, categorize and leverage issues for software engineering needs. Who, however, cares about filing issues? What kind of issues are reported in issue trackers? What kind of correlation exist between issue reporting and the success of software projects? In this study, we address the need for answering such questions by performing an empirical study on a hundred thousands of open source projects. After filtering relevant trackers, the study used about 20,000 projects. We investigate and answer various research questions on the popularity and impact of issue trackers.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
Quality and productivity outcomes relating to continuous integration in GitHub
Vasilescu, B., Yu, Y., Wang, H., Devanbu, P., & Filkov, V. (2015) · Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering · doi:10.1145/2786805.2786850 · Cited by 406
Curating GitHub for engineered software projects
Munaiah, N., Kroh, S., Cabrey, C., & Nagappan, M. (2017) · Empirical Software Engineering · doi:10.1007/s10664-017-9512-6 · Cited by 365
“(2014) identified this noise as one of the nine perils to be aware of when mining GitHub data for software engineering research. The situation is compounded by the sheer volume of repositories contained in these forges. As of June, 2016, GitHub alone hosted over 38 million repositories2 and this number is rapidly incr…”
BackgroundMethodInfluentialAn in-depth study of the promises and perils of mining GitHub
Kalliamvakou, E., Gousios, G., Blincoe, K., Singer, L., German, D. M., & Damian, D. (2016) · Empirical Software Engineering · doi:10.1007/s10664-015-9393-5 · Cited by 282
DeepFakes: uncovering hardcore open source on GitHub
Winter, R., & Salter, A. (2020) · Porn Studies · doi:10.1080/23268743.2019.1642794 · Cited by 42
Metadata
- Authors
- Bissyande, T. F., Lo, D., Jiang, L., Reveillere, L., Klein, J., & Traon, Y. L.
- Venue
- 2013 IEEE 24th International Symposium on Software Reliability Engineering (ISSRE)
- Publisher
- IEEE
- Published
- 2013-11
- Pages
- 188-197
- OpenAlex
- W1966769823
- Cited by
- 178
- References
- 0
- FWCI
- 6.73
- Type
- conference paper
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Got issues? Who cares about it? A large scale investigation of issue trackers from GitHub. https://app.cochat.ai/papers/10.1109/issre.2013.6698918
- The paper
- Bissyande, T. F., Lo, D., Jiang, L., Reveillere, L., Klein, J., & Traon, Y. L. (2013). Got issues? Who cares about it? A large scale investigation of issue trackers from GitHub. 2013 IEEE 24th International Symposium on Software Reliability Engineering (ISSRE). https://doi.org/10.1109/issre.2013.6698918
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.