Authors: Olga Baysal Reid Holmes Michael W. Godfrey
Venue: ICSE 2013 35th International Conference on Software Engineering (ICSE), pp. 1185-1188, 2013
Year: 2013
Abstract: Issue tracking systems play a central role in ongoing software development; they are used by developers to support collaborative bug fixing and the implementation of new features, but they are also used by other stakeholders including managers, QA, and end-users for tasks such as project management, communication and discussion, code reviews, and history tracking. Most such systems are designed around the central metaphor of the“issue” (bug, defect, ticket, feature, etc.), yet increasingly this model seems ill fitted to the practical needs of growing software projects; for example, our analysis of interviews with 20 Mozilla developers who use Bugzilla heavily revealed that developers face challenges maintaining a global understanding of the issues they are involved with, and that they desire improved support for situational awareness that is difficult to achieve with current issue management systems. In this paper we motivate the need for personalized issue tracking that is centered around the information needs of individual developers together with improved logistical support for the tasks they perform. We also describe an initial approach to implement such a system - extending Bugzilla - that enhances a developer's situational awareness of their working context by providing views that are tailored to specific tasks they frequently perform; we are actively improving this prototype with input from Mozilla developers.
BibTeX:
@inproceedings{olgabaysal2013sapits,
author = "Olga Baysal and Reid Holmes and Michael W. Godfrey",
title = "Situational awareness: Personalizing issue tracking systems",
year = "2013",
pages = "1185-1188",
booktitle = "Proceedings of 2013 35th International Conference on Software Engineering (ICSE)"
}
Plain Text:
Olga Baysal, Reid Holmes, and Michael W. Godfrey, "Situational awareness: Personalizing issue tracking systems," 2013 35th International Conference on Software Engineering (ICSE), pp. 1185-1188