[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
10.5555/2486788.2486834acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
research-article

PorchLight: a tag-based approach to bug triaging

Published: 18 May 2013 Publication History

Abstract

Bug triaging is an important activity in any software development project. It involves developers working through the set of unassigned bugs, determining for each of the bugs whether it represents a new issue that should receive attention, and, if so, assigning it to a developer and a milestone. Current tools provide only minimal support for bug triaging and especially break down when developers must triage a large number of bug reports, since those reports can only be viewed one-by-one. This paper presents PorchLight, a novel tool that uses tags, attached to individual bug reports by queries expressed in a specialized bug query language, to organize bug reports into sets so developers can explore, work with, and ultimately assign bugs effectively in meaningful groups. We describe the challenges in supporting bug triaging, the design decisions upon which PorchLight rests, and the technical aspects of the implementation. We conclude with an early evaluation that involved six professional developers who assessed PorchLight and its potential for their day-to-day triaging duties.

References

[1]
J.  Anvik,  L.  Hiew,  and  G.C.  Murphy,  “Who  should  fix  this   bug?,”  28th ICSE, 2006, pp. 361–370.
[2]
T.  Downer,  “Some  Clarification  and Musings”  Available:   http://tylerdowner.wordpress.com/2011/08/27/someclarification-and-musings/.
[3]
G. Ruhe and M.O. Saliu,  “The  Art  and  Science  of  Software   Release  Planning,”  IEEE Software, vol. 22, Nov. 2005, pp. 47–53.
[4]
M.  Li,  M.  Huang,  F.  Shu,  and  J.  Li,  “A  risk-driven method for eXtreme  programming  release  planning,”  28th ICSE, 2006, pp. 423–430.
[5]
A. Ngo-The, G. Ruhe,  and  W.  Shen,  “Release  Planning  under   Fuzzy  Effort  Constraints,”  3rd International Conference on Cognitive Informatics, 2004, pp. 168–175.
[6]
M. Cohn, Succeeding with Agile: Software Development Using Scrum, Addison-Wesley Professional, 2009.
[7]
P.J. Guo,  T.  Zimmerman,  N.  Nagappan,  and  B.  Murphy,  “‘Not   My  Bug!’  and  Other  Reasons  for  Software  Bug  Report   Reassignments,”  CSCW, 2011.
[8]
G.  Jeong,  S.  Kim,  and  T.  Zimmermann,  “Improving  bug  triage   with  bug  tossing  graphs,”  ESEC/FSE, 2009.
[9]
S. Breu, R. Premraj, J. Sillito, and T. Zimmermann, “Information  needs  in  bug  reports,”  CSCW, 2010.
[10]
“Bug  tracking  with  JIRA”  Available:   http://www.atlassian.com/software/jira/tour/bug-tracking.jsp.
[11]
“Bugzilla”  Available:  http://www.bugzilla.org/.
[12]
“FogBugz  from  Fog  Creek  Software”  Available:   http://www.fogcreek.com/fogbugz/.
[13]
“The  Trac  Project”  Available:  http://trac.edgewall.org/.
[14]
D. Bertram, A. Voida, S. Greenberg, and R. Walker, “Communication,  collaboration,  and  bugs,”  CSCW, 2010, pp. 291–300.
[15]
J.  Aranda  and  G.  Venolia,  “The  secret  life  of  bugs:  Going  past   the  errors  and  omissions  in  software  repositories,”  31st ICSE, 2009, pp. 298–308.
[16]
“Triaging  Bugs  -The  Chromium  Projects”  Available:   http://www.chromium.org/getting-involved/bug-triage.
[17]
“Guide  to  Triaging  Bugs  for  Firefox”  Available:   https://quality.mozilla.org/docs/bugzilla/guide-to-triagingbugs-for-firefox/.
[18]
D.  Cook,  “Improving  Bug  Triage  with  User  Pain”  Available:   http://www.lostgarden.com/2008/05/improving-bug-triagewith-user-pain.html.
[19]
M.  Cepl,  “Letter  to  my  successors  (or  what  do  I  know  about   the  Xorg  bug  triage)”  Available:   http://luther.ceplovi.cz/blog/2011/11/letter-to-my-successorsor-what-do-i-know-about-the-xorg-bug-triage/.
[20]
S.  Just,  R.  Premraj,  and  T.  Zimmermann,  “Towards  the  next   generation  of  bug  tracking  systems,”  VL/HCC, 2008, pp. 82– 85.
[21]
G.  Bortis  and  A.  van  der  Hoek,  “TeamBugs:  a  collaborative   bug  tracking  tool,”  CHASE, 2011, pp. 69–71.
[22]
L.  Hiew,  “Assisted  detection  of  duplicate  bug  reports,”   Master’s  thesis,  The  University  of  British  Columbia,  2006.
[23]
P.  Runeson,  M.  Alexandersson,  and  O.  Nyholm,  “Detection  of   Duplicate Defect Reports Using Natural Language Processing,”  29th ICSE, 2007, pp. 499–510.
[24]
X. Wang,  L.  Zhang,  T.  Xie,  J.  Anvik,  and  J.  Sun,  “An   approach to detecting duplicate bug reports using natural language  and  execution  information,”  13th ICSE, 2008.
[25]
K.  Somasundaram  and  G.C.  Murphy,  “Automatic   categorization of bug reports using latent Dirichlet  allocation,”   5th ISEC, 2012, pp. 125–130.
[26]
A. Tamrawi, T.T. Nguyen, J. Al-Kofahi, and T.N. Nguyen, “Fuzzy  set-based  automatic  bug  triaging  (NIER  track),”  33rd ICSE, 2011, pp. 884–887.
[27]
M. Linares-Vasquez, K. Hossen, H. Dang, H. Kagdi, M. Gethers,  and  D.  Poshyvanyk,  “Triaging  Incoming  Change   Requests:  Bug  or  Commit  History,  or  Code  Authorship?,”   28th ICSM, 2012.
[28]
C.A. Halverson, J.B. Ellis, C. Danis, and W.A. Kellogg, “Designing  task  visualizations  to  support  the  coordination  of   work in software  development,”  CSCW, 2006, pp. 39–48.
[29]
J.  Anvik  and  G.C.  Murphy,  “Reducing  the  effort  of  bug  report   triage: Recommenders for development-oriented  decisions,”   ACM TOSEM, vol. 20, Aug. 2011, pp. 10:1–10:35.
[30]
Y. Koren, E. Liberty, Y. Maarek, and R. Sandler, “Automatically  tagging  email  by  leveraging  other  users’   folders,”  KDD, 2011, pp. 913–921.
[31]
C. Treude and M.-A.  Storey,  “How  tagging  helps  bridge  the   gap between social and technical aspects in software development,”  31st ICSE, 2009, pp. 12 –22.
[32]
M.  Ames  and  M.  Naaman,  “Why  we  tag:  motivations  for   annotation  in  mobile  and  online  media,”  CHI, 2007, pp. 971– 980.

Cited By

View all
  • (2021)Fast Outage Analysis of Large-scale Production Clouds with Service Correlation MiningProceedings of the 43rd International Conference on Software Engineering10.1109/ICSE43902.2021.00085(885-896)Online publication date: 22-May-2021
  • (2019)An empirical investigation of incident triage for online service systemsProceedings of the 41st International Conference on Software Engineering: Software Engineering in Practice10.1109/ICSE-SEIP.2019.00020(111-120)Online publication date: 27-May-2019
  • (2018)Towards a classification of bugs to facilitate software maintainability tasksProceedings of the 1st International Workshop on Software Qualities and Their Dependencies10.1145/3194095.3194101(25-32)Online publication date: 28-May-2018
  • Show More Cited By

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM Conferences
ICSE '13: Proceedings of the 2013 International Conference on Software Engineering
May 2013
1561 pages
ISBN:9781467330763

Sponsors

Publisher

IEEE Press

Publication History

Published: 18 May 2013

Check for updates

Qualifiers

  • Research-article

Conference

ICSE '13
Sponsor:

Acceptance Rates

Overall Acceptance Rate 276 of 1,856 submissions, 15%

Upcoming Conference

ICSE 2025

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)6
  • Downloads (Last 6 weeks)0
Reflects downloads up to 13 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2021)Fast Outage Analysis of Large-scale Production Clouds with Service Correlation MiningProceedings of the 43rd International Conference on Software Engineering10.1109/ICSE43902.2021.00085(885-896)Online publication date: 22-May-2021
  • (2019)An empirical investigation of incident triage for online service systemsProceedings of the 41st International Conference on Software Engineering: Software Engineering in Practice10.1109/ICSE-SEIP.2019.00020(111-120)Online publication date: 27-May-2019
  • (2018)Towards a classification of bugs to facilitate software maintainability tasksProceedings of the 1st International Workshop on Software Qualities and Their Dependencies10.1145/3194095.3194101(25-32)Online publication date: 28-May-2018
  • (2017)Defect Triage MeetingsProceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering10.1145/3084226.3084281(74-77)Online publication date: 15-Jun-2017
  • (2017)Improving Automated Bug Triaging with Specialized Topic ModelIEEE Transactions on Software Engineering10.1109/TSE.2016.257645443:3(272-297)Online publication date: 1-Mar-2017
  • (2015)Are these bugs really "normal"?Proceedings of the 12th Working Conference on Mining Software Repositories10.5555/2820518.2820550(258-268)Online publication date: 16-May-2015
  • (2015)Using developer-interaction trails to triage change requestsProceedings of the 12th Working Conference on Mining Software Repositories10.5555/2820518.2820532(88-98)Online publication date: 16-May-2015
  • (2014)Amalgamating source code authors, maintainers, and change proneness to triage change requestsProceedings of the 22nd International Conference on Program Comprehension10.1145/2597008.2597147(130-141)Online publication date: 2-Jun-2014
  • (2014)Improving enterprise software maintenance efficiency through mining software repositories in an industry contextCompanion Proceedings of the 36th International Conference on Software Engineering10.1145/2591062.2591085(706-709)Online publication date: 31-May-2014

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media