DMCA
No Issue Left Behind: Reducing Information Overload in Issue Tracking
| Citations: | 1 - 0 self |
BibTeX
@MISC{Baysal_noissue,
author = {Olga Baysal and Reid Holmes and Michael W. Godfrey},
title = {No Issue Left Behind: Reducing Information Overload in Issue Tracking},
year = {}
}
Share
 |
 |
 |
 |
||
OpenURL
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 ap-proach is motivated by a grounded theory study of devel-oper 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 un-derstand the surrounding technical context. From the qual-itative study, we uncovered a model of the kinds of informa-tion elements that are essential for developers in completing their daily tasks, and from this model we built a tool or-ganized around customized issue-tracking dashboards. Fur-ther quantitative and qualitative evaluation demonstrated that this dashboard-like approach to issue tracking can re-duce the volume of irrelevant emails by over 99 % and also improve support for specific issue-tracking tasks.
Keyphrases
information overload issue tracking constant influx customized issue-tracking dashboard particular information new data informa-tion element developer-centric approach customized view raw information dashboard-like approach technical context vast majority devel-oper comment grounded theory study qual-itative study modern software development tool irrelevant email issue tracker multi-purpose tool qualitative evaluation developer-specific task immense amount developer situational awareness project repository specific issue-tracking task daily task
