Factors characterizing reopened issues: A case study

Bora Caglayan, Ayse Tosun Misirli, Andriy Miranskyy, Burak Turhan, Ayse Bener

Research output: Chapter in Book/Report/Conference proceedingConference PaperResearchpeer-review

9 Citations (Scopus)

Abstract

Background: Reopened issues may cause problems in managing software maintenance effort. In order to take actions that will reduce the likelihood of issue reopening the possible causes of bug reopens should be analysed. Aims: In this paper, we investigate potential factors that may cause issue reopening. Method: We have extracted issue activity data from a large release of an enterprise software product. We consider four dimensions, namely developer activity, issue proximity network, static code metrics of the source code changed to fix an issue, issue reports and fixes as possible factors that may cause issue reopening. We have done exploratory analysis on data. We build logistic regression models on data in order to identify key factors leading issue reopening. We have also conducted a survey regarding these factors with the QA Team of the product and interpreted the results. Results: Our results indicate that centrality in the issue proximity network and developer activity are important factors in issue reopening. We have also interpreted our results with the QA Team to point out potential implications for practitioners. Conclusions: Quantitative findings of our study suggest that issue complexity and developers workload play an important role in triggering issue reopening.

Original languageEnglish
Title of host publicationPROMISE 2012 - 8th International Conference on Predictive Models in Software Engineering, Co-located with ESEM 2012
Pages1-10
Number of pages10
DOIs
Publication statusPublished - 26 Oct 2012
Externally publishedYes
Event8th International Conference on Predictive Models in Software Engineering, PROMISE 2012 - Co-located with ESEM 2012 - Lund, Sweden
Duration: 21 Sep 201222 Sep 2012

Conference

Conference8th International Conference on Predictive Models in Software Engineering, PROMISE 2012 - Co-located with ESEM 2012
CountrySweden
CityLund
Period21/09/1222/09/12

Keywords

  • Issue management
  • Issue reopening
  • Issue repository
  • Software maintenance

Cite this

Caglayan, B., Misirli, A. T., Miranskyy, A., Turhan, B., & Bener, A. (2012). Factors characterizing reopened issues: A case study. In PROMISE 2012 - 8th International Conference on Predictive Models in Software Engineering, Co-located with ESEM 2012 (pp. 1-10) https://doi.org/10.1145/2365324.2365327