Strengthening the Case for Pair Programming
IEEE Software
The Art of Software Testing
Proceedings of the 28th international conference on Software engineering
How Long Will It Take to Fix This Bug?
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Determining Implementation Expertise from Bug Reports
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
An approach to detecting duplicate bug reports using natural language and execution information
Proceedings of the 30th international conference on Software engineering
IEEE Transactions on Software Engineering
Optimized Resource Allocation for Software Release Planning
IEEE Transactions on Software Engineering
Characterizing and predicting which bugs get fixed: an empirical study of Microsoft Windows
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Predicting the fix time of bugs
Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering
Studying the Impact of Social Structures on Software Quality
ICPC '10 Proceedings of the 2010 IEEE 18th International Conference on Program Comprehension
Measuring and predicting software productivity: A systematic map and review
Information and Software Technology
"Not my bug!" and other reasons for software bug report reassignments
Proceedings of the ACM 2011 conference on Computer supported cooperative work
Fuzzy set-based automatic bug triaging (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Reducing the effort of bug report triage: Recommenders for development-oriented decisions
ACM Transactions on Software Engineering and Methodology (TOSEM)
A Methodology for Collecting Valid Software Engineering Data
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
Issue management is one of the major challenges of software development teams. Balanced workload allocation of developers who are responsible for the maintenance of the software product would impact the long-term reliability of the product. In this paper, we analyse the issue report, issue ownership, and issue resolve patterns of two large software products over a period of time. We use GINI index to estimate the inequalities in issue ownership over time. Our results indicate that a small group of developers tends to take the ownership of a large portion of new issues especially when the active issue count is relatively high in the software development life cycle. We discuss the implications of this trend and propose long-term issue management strategies to deal with them.