Analyzing and relating bug report data for feature tracking

Fischer, Michael; Pinzger, Martin; Gall, Harald C.

doi:10.1109/wcre.2003.1287240

Cited by 89 publications

(64 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [7] they also combined their approach with features. Another project that considers additional data sources is Hipikat by DavorČubranić and Gail Murphy [5].…”

Section: Related Workmentioning

confidence: 99%

Preprocessing CVS data for fine-grained analysis

Zimmermann

Weißgerber

2004

"International Workshop on Mining Software Repositories (MSR 2004)" W17S Workshop - 26th International Conference on Software E

175

131

View full text Add to dashboard Cite

show abstract

“…In [7] they also combined their approach with features. Another project that considers additional data sources is Hipikat by DavorČubranić and Gail Murphy [5].…”

Section: Related Workmentioning

confidence: 99%

Preprocessing CVS data for fine-grained analysis

Zimmermann

Weißgerber

2004

"International Workshop on Mining Software Repositories (MSR 2004)" W17S Workshop - 26th International Conference on Software E

175

131

View full text Add to dashboard Cite

show abstract

“…We call it Loner, because in case of a missing interlinking the according commit or issue is without any relationship. An example is the issue AMBARI-3412 4 of Ambari (P2) and the associated, but not linked commit f2146a41 5 . The problem is that the commit message contains the issue key in the wrong format and therefore the link is not detected.…”

Section: B Apache Project Surveymentioning

confidence: 99%

“…For this reason, various research studies investigated possible ways to recover missing links (e.g., [2], [4], [5]). Researchers proposed heuristics (e.g., [6], [7]) to automatically recover missing links by mining issue tracking platforms and commit messages in logs of version control systems (VCS).…”

Section: Introductionmentioning

confidence: 99%

Discovering Loners and Phantoms in Commit and Issue Data

Schermann

Brandtner

Panichella

et al. 2015

2015 IEEE 23rd International Conference on Program Comprehension

View full text Add to dashboard Cite

The interlinking of commit and issue data has become a de-facto standard in software development. Modern issue tracking systems, such as JIRA, automatically interlink commits and issues by the extraction of identifiers (e.g., issue key) from commit messages. However, the conventions for the use of interlinking methodologies vary between software projects. For example, some projects enforce the use of identifiers for every commit while others have less restrictive conventions. In this work, we introduce a model called PaLiMod to enable the analysis of interlinking characteristics in commit and issue data. We surveyed 15 Apache projects to investigate differences and commonalities between linked and non-linked commits and issues. Based on the gathered information, we created a set of heuristics to interlink the residual of non-linked commits and issues. We present the characteristics of Loners and Phantoms in commit and issue data. The results of our evaluation indicate that the proposed PaLiMod model and heuristics enable an automatic interlinking and can indeed reduce the residual of non-linked commits and issues in software projects. Abstract-The interlinking of commit and issue data has become a de-facto standard in software development. Modern issue tracking systems, such as JIRA, automatically interlink commits and issues by the extraction of identifiers (e.g., issue key) from commit messages. However, the conventions for the use of interlinking methodologies vary between software projects. For example, some projects enforce the use of identifiers for every commit while others have less restrictive conventions. In this work, we introduce a model called PaLiMod to enable the analysis of interlinking characteristics in commit and issue data. We surveyed 15 Apache projects to investigate differences and commonalities between linked and non-linked commits and issues. Based on the gathered information, we created a set of heuristics to interlink the residual of non-linked commits and issues. We present the characteristics of Loners and Phantoms in commit and issue data. The results of our evaluation indicate that the proposed PaLiMod model and heuristics enable an automatic interlinking and can indeed reduce the residual of non-linked commits and issues in software projects.

show abstract

“…Another approach that takes modification and problem reports into account is presented by Fischer, Pinzger and Gall in [3]. They use this data to analyze the evolution of a given software project and to track and to identify hidden relations between different features of the software system.…”

Section: Related Workmentioning

confidence: 99%