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

No issue left behind: reducing information overload in issue tracking

Published: 11 November 2014 Publication History

Abstract

Modern software development tools such as issue trackers are often complex and multi-purpose tools that provide access to an immense amount of raw information. Unfortunately, developers sometimes feel frustrated when they cannot easily obtain the particular information they need for a given task; furthermore, the constant influx of new data — the vast majority of which is irrelevant to their task at hand — may result in issues being "dropped on the floor". In this paper, we present a developer-centric approach to issue tracking that aims to reduce information overload and improve developers' situational awareness. Our approach is motivated by a grounded theory study of developer comments, which suggests that customized views of a project's repositories that are tailored to developer-specific tasks can help developers better track their progress and understand the surrounding technical context. From the qualitative study, we uncovered a model of the kinds of information elements that are essential for developers in completing their daily tasks, and from this model we built a tool organized around customized issue-tracking dashboards. Further quantitative and qualitative evaluation demonstrated that this dashboard-like approach to issue tracking can reduce the volume of irrelevant emails by over 99% and also improve support for specific issue-tracking tasks.

References

[1]
Atlassian. Jira. http: //www.atlassian.com/software/jira/overview.
[2]
O. Baysal and R. Holmes. A Qualitative Study of Mozilla’s Process Management Practices. Technical Report CS-2012-10, David R. Cheriton School of Computer Science, University of Waterloo, Waterloo, Canada, June 2012. Also available online 5 http://www.bugzilla.org/installation-list/ http://www.cs.uwaterloo.ca/research/tr/2012/ CS-2012-10.pdf.
[3]
O. Baysal, R. Holmes, and M. W. Godfrey. Situational Awareness: Personalizing Issue Tracking Systems. In Proc. of the New Ideas and Emerging Results (NIER) Track, the 35th Int. Conf. on Soft. Eng., 2013.
[4]
D. Bertram, A. Voida, S. Greenberg, and R. Walker. Communication, collaboration, and bugs: The social nature of issue tracking in small, collocated teams. In Proc. of the ACM Conf. on Computer Supported Cooperative Work, pages 291–300, 2010.
[5]
M. Best. The Bugzilla Anthropology. https://wiki.mozilla.org/Bugzilla_Anthropology.
[6]
N. Bettenburg and A. Begel. Deciphering the story of software development through frequent pattern mining. In Proceedings of the 2013 International Conference on Software Engineering, pages 1197–1200, 2013.
[7]
N. Bettenburg, S. Just, A. Schröter, C. Weiss, R. Premraj, and T. Zimmermann. What makes a good bug report? In Proc. of the ACM-SIGSOFT Intl. Symposium on Foundations of Software Engineering, pages 308–318, 2008.
[8]
J. T. Biehl, M. Czerwinski, G. Smith, and G. G. Robertson. Fastdash: A visual dashboard for fostering awareness in software teams. In Proc. of the ACM-SIGCHI Conf. on Human Factors in Computing Systems, pages 1313–1322, 2007.
[9]
S. Breu, R. Premraj, J. Sillito, and T. Zimmermann. Information needs in bug reports: Improving cooperation between developers and users. In Proc. of the ACM Conf. on Computer Supported Cooperative Work, pages 301–310, 2010.
[10]
G. Britz. Improving Performance Through Statistical Thinking. ASQ Quality Press, 2000.
[11]
Y. Brun, R. Holmes, M. D. Ernst, and D. Notkin. Crystal: Precise and unobtrusive conflict warnings. In Proc. of ESEC-FSE Tool Demo, 2011.
[12]
L.-T. Cheng, S. Hupfer, S. Ross, and J. Patterson. Jazzing up eclipse with collaborative tools. In Proc. of the 2003 OOPSLA Workshop on Eclipse Technology eXchange, pages 45–49, 2003.
[13]
M. Cherubini, G. Venolia, R. DeLine, and A. J. Ko. Let’s go to the whiteboard: how and why software developers use drawings. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, pages 557–566, 2007.
[14]
J. Creswell. Research Design: Qualitative, Quantitative, and Mixed Methods Approaches. SAGE Publications, 2003.
[15]
D. Cubrani´ c and G. C. Murphy. Hipikat: Recommending pertinent software development artifacts. In Proc. of the Intl. Conf. on Software Engineering, pages 408–418, Washington, DC, USA, 2003. IEEE Computer Society.
[16]
K. Czarnecki, Z. Malik, and R. Lotufo. Modelling the “hurried” bug report reading process to summarize bug reports. In Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM), pages 430–439, Washington, DC, USA, 2012. IEEE Computer Society.
[17]
D. Damian, L. Izquierdo, J. Singer, and I. Kwan. Awareness in the wild: Why communication breakdowns occur. In Global Software Engineering, 2007. ICGSE 2007. Second IEEE International Conference on, pages 81–90, 2007.
[18]
R. DeLine, M. Czerwinski, B. Meyers, G. Venolia, S. Drucker, and G. Robertson. Code thumbnails: Using spatial memory to navigate source code. In Proc. of the Visual Languages and Human-Centric Computing, pages 11–18, 2006.
[19]
R. DeLine, M. Czerwinski, and G. Robertson. Easing program comprehension by sharing navigation data. In Proc. of the IEEE Symposium on Visual Languages and Human-Centric Computing, pages 241–248, 2005.
[20]
M. R. Endsley. Toward a theory of situation awareness in dynamic systems. Human factors, 37(1):32–64, 1995.
[21]
ENTP. Lighthouse. https://lighthouseapp.com/.
[22]
J. Espinosa, S. Slaughter, R. Kraut, and J. Herbsleb. Team knowledge and coordination in geographically distributed software development. J. Manage. Inf. Syst., 24(1):135–169, July 2007.
[23]
C. Fernstrom, K.-H. Narfelt, and L. Ohlsson. Software factory principles, architecture, and experiments. Software, IEEE, 9(2):36–44, march 1992.
[24]
D. Freelon. ReCal2: Reliability for 2 coders. http://dfreelon.org/utils/recalfront/recal2/.
[25]
T. Fritz and G. C. Murphy. Determining relevancy: how software developers determine relevant information in feeds. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, pages 1827–1830, 2011.
[26]
J. Froehlich and P. Dourish. Unifying artifacts and activities in a visual tool for distributed software development teams. In Proc. of the ACM/IEEE Intl. Conf. on Software Engineering, pages 387–396, 2004.
[27]
C. Godart, P. Molli, G. Oster, O. Perrin, H. Skaf-Molli, P. Ray, and F. Rabhi. The toxicfarm integrated cooperation framework for virtual teams. In Distributed and parallel databases: special issue on teamware technologies, pages 67–88, 2004.
[28]
C. Gutwin, R. Penner, and K. Schneider. Group awareness in distributed software development. In Proceedings of the 2004 ACM conference on Computer supported cooperative work, CSCW ’04, pages 72–81, New York, NY, USA, 2004. ACM.
[29]
J. D. Herbsleb and R. E. Grinter. Architectures, coordination, and distance: Conway’s law and beyond. IEEE Softw., 16(5):63–70, Sept. 1999.
[30]
R. Holmes and R. J. Walker. Customized awareness: Recommending relevant external change events. In Proc. of the ACM/IEEE Intl. Conf. on Software Engineering, pages 465–474, 2010.
[31]
C.-Y. Jang, C. Steinfield, and B. Pfaff. Virtual team awareness and groupware support: an evaluation of the teamscope system. Int. J. Hum.-Comput. Stud., 56(1):109–126, Jan. 2002.
[32]
S. Just, R. Premraj, and T. Zimmermann. Towards the next generation of bug tracking systems. In IEEE Symposium on Visual Languages and Human-Centric Computing, pages 82 –85, Sept. 2008.
[33]
R. Kadia. Issues encountered in building a flexible software development environment: lessons from the arcadia project. In Proceedings of the fifth ACM SIGSOFT symposium on Software development environments, SDE 5, pages 169–180, 1992.
[34]
M. Kersten and G. C. Murphy. Using task context to improve programmer productivity. In Proc. of the ACM-SIGSOFT Intl. Symposium on Foundations of Software Engineering, pages 1–11, 2006.
[35]
O. Kononenko, O. Baysal, R. Holmes, and M. W. Godfrey. DASHboards: Enhancing developer situational awareness. In Proceedings of the Formal Demonstration Track, at the 36th International Conference on Software Engineering, ICSE’14, 2013.
[36]
M. Miles and A. Huberman. Qualitative Data Analysis: An Expanded Sourcebook. SAGE Publications, 1994.
[37]
S. Rastkar, G. C. Murphy, and G. Murray. Summarizing software artifacts: a case study of bug reports. In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1, pages 505–514, New York, NY, USA, 2010. ACM.
[38]
A. Sarma, Z. Noroozi, and A. van der Hoek. Palantir: Raising awareness among configuration management workspaces. In Proc. of the ACM/IEEE Intl. Conf. on Software Engineering, pages 444–454, 2003.
[39]
E. Software. Trac. http://trac.edgewall.org/.
[40]
I. Steinmacher, A. P. Chaves, and M. A. Gerosa. Awareness support in global software development: a systematic review based on the 3c collaboration model. In Proceedings of the 16th international conference on Collaboration and technology, pages 185–201, Berlin, Heidelberg, 2010.
[41]
M.-A. Storey, L.-T. Cheng, I. Bull, and P. Rigby. Shared waypoints and social tagging to support collaboration in software development. In Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work, CSCW ’06, pages 195–198, 2006.
[42]
C. Treude and M.-A. Storey. Awareness 2.0: staying aware of projects, developers and tasks using dashboards and feeds. In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1, pages 365–374, 2010.
[43]
G. Venolia. Textual allusions to artifacts in software-related repositories. In Proc. of the Intl. Workshop on Mining Software Repositories, pages 151–154, 2006.
[44]
T. Zimmermann, R. Premraj, J. Sillito, and S. Breu. Improving bug tracking systems. In Proc. of the Intl. Conf. on Software Engineering — Companion Volume, pages 247 –250, May 2009.
[45]
R. W. Zmud. Management of large software development efforts. MIS Q., 4(2):45–55, June 1980. Introduction Qualitative Study Data Collection Data Analysis A New Model of Issue Tracking Model Categories Situational Awareness Task Support Expressiveness Key Information Sets Issues Patches and Reviews Model Summary DASH: Reducing Information Overload Background High-Fidelity Prototype Prototype Evaluation DASH Tool Tool Validation Related Work Discussion Shortcomings Deployment Threats and Limitations Conclusion Acknowledgements References

Cited By

View all
  • (2024)Characterizing Usability Issue Discussions in Open Source Software ProjectsProceedings of the ACM on Human-Computer Interaction10.1145/36373078:CSCW1(1-26)Online publication date: 26-Apr-2024
  • (2024)Improving Issue-PR Link Prediction via Knowledge-Aware Heterogeneous Graph LearningIEEE Transactions on Software Engineering10.1109/TSE.2024.340844850:7(1901-1920)Online publication date: 1-Jul-2024
  • (2024)Automating Static Code Analysis Through CI/CD Pipeline Integration2024 IEEE International Conference on Software Analysis, Evolution and Reengineering - Companion (SANER-C)10.1109/SANER-C62648.2024.00021(119-125)Online publication date: 12-Mar-2024
  • Show More Cited By

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM Conferences
FSE 2014: Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering
November 2014
856 pages
ISBN:9781450330565
DOI:10.1145/2635868
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than the author(s) must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected].

Sponsors

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 11 November 2014

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. Developer dashboards
  2. information needs
  3. issue tracking
  4. personalization
  5. situational awareness

Qualifiers

  • Research-article

Conference

SIGSOFT/FSE'14
Sponsor:

Acceptance Rates

Overall Acceptance Rate 17 of 128 submissions, 13%

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)56
  • Downloads (Last 6 weeks)6
Reflects downloads up to 19 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2024)Characterizing Usability Issue Discussions in Open Source Software ProjectsProceedings of the ACM on Human-Computer Interaction10.1145/36373078:CSCW1(1-26)Online publication date: 26-Apr-2024
  • (2024)Improving Issue-PR Link Prediction via Knowledge-Aware Heterogeneous Graph LearningIEEE Transactions on Software Engineering10.1109/TSE.2024.340844850:7(1901-1920)Online publication date: 1-Jul-2024
  • (2024)Automating Static Code Analysis Through CI/CD Pipeline Integration2024 IEEE International Conference on Software Analysis, Evolution and Reengineering - Companion (SANER-C)10.1109/SANER-C62648.2024.00021(119-125)Online publication date: 12-Mar-2024
  • (2024)The role of surprisal in issue trackersEmpirical Software Engineering10.1007/s10664-024-10587-w30:1Online publication date: 23-Nov-2024
  • (2023) To Follow or Not to Follow: Understanding Issue/Pull-Request Templates on GitHub IEEE Transactions on Software Engineering10.1109/TSE.2022.322405349:4(2530-2544)Online publication date: 1-Apr-2023
  • (2023)Improved Management of Issue Dependencies in Issue Trackers of Large Collaborative ProjectsIEEE Transactions on Software Engineering10.1109/TSE.2022.321216649:4(2128-2148)Online publication date: 1-Apr-2023
  • (2020)ArguLens: Anatomy of Community Opinions On Usability Issues Using Argumentation ModelsProceedings of the 2020 CHI Conference on Human Factors in Computing Systems10.1145/3313831.3376218(1-14)Online publication date: 21-Apr-2020
  • (2020)Characterizing Task-Relevant Information in Natural Language Software Artifacts2020 IEEE International Conference on Software Maintenance and Evolution (ICSME)10.1109/ICSME46990.2020.00052(476-487)Online publication date: Sep-2020
  • (2020)Solution for Information Overload Using Faceted Search–A ReviewIEEE Access10.1109/ACCESS.2020.30055368(119554-119585)Online publication date: 2020
  • (2019)On reliability of patch correctness assessmentProceedings of the 41st International Conference on Software Engineering10.1109/ICSE.2019.00064(524-535)Online publication date: 25-May-2019
  • Show More Cited By

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