A Dataset of High Impact Bugs:
Manually-Classified Issue Reports

×	11
111
Masao Ohira , Yutaro Kashiwa , Yosuke Yamatani , Hayato Yoshiyuki , Yoshiya Maeda ,1Wakayama University, Japan

Nachai Limsettho2, Keisuke Fujino2, Hideaki Hata2, Akinori Ihara2 and Kenichi Matsumoto2

2Technology, Japan

Background

2Nara Institute of Science andWhich bug
should I ﬁx ﬁrst?

session error!
wrong docs! hung up!
canʼt login!
lost my data!
wrong result!
ManagerA great number of bugs are found not onlyUser
before but also after releasing products. Amanager must prioritize reported bugs to beﬁxed. Many studies proposed methods to support bug-triaging. However, in these studies, eachﬁxed
bug is equally treated without considering its impact on the bug management process andsoftware products.

Dataset

Process bug
A process bug is a bug that aﬀects a bug
management process.
n Blocking bug [Valdiviaʼ14 etc.]
A bug that blocks other bugs
targetfrom being ﬁxedn Surprising bug [Shihabʼ11]！
A bug that appears inu n e x p e c t e d t i m i n g a n d pre-release post-releaselocationn Dormant bug [Chenʼ14]
Dormant
A bug that was introduced inperiodone version of a system but
was not reported until thenext immediate version

Issue report data has been collected fromthe Apache Ambari, Camel, Derby, andWicket projects which JIRA is used for
managing reported issues.
All the issues inNov. 20 2014
Ambari
Camel
Derby
Wicket

8,389
8,063
6,772
5,769

($$')$

&)$
&$$
%)$
%$$)$$ 

Product bug

Dataset: http://goo.gl/r53j7w



 

)%

%

(

'

+$

&**

%

*

&*

'(

,

'##
&(#

Camel&## %(#
%##
$(#
$##
(##

 





 



$(+

'&

$%

$(

&'

+%&#

$$#

)

$,

)$

'*

&""
%'"

Derby%""

 $'"
$""
#'"
#""
'"
"


 

 



%(

$$

&

$#

&"

%

###

##'

#*

()

(#

#*&

'##
&(#Wicket&##

Reference%(# [Valdivia’14] H. Valdivia Garcia and E. Shihab, “Characterizing and predicting blocking bugs in open source projects,” in Proc. ofMSR ’14, 2014, pp. 72–81.
[Chen’14] T.-H. Chen, M. Nagappan, E. Shihab, and A. E. Hassan, “An empirical study of dormant bugs,” in Proc. of MSR ’14,2014, pp. 82–91.
[Shihab’11] E. Shihab, A. Mockus, Y. Kamei, B. Adams, and A. E. Hassan, “High- impact defects: A study of breakage andsurprise defects,” in Proc. of ESEC/FSE ’11, 2011, pp. 300–310.
[Gegick’10] M. Gegick, P. Rotella, and T. Xie, “Identifying security bug reports via text mining: An industrial case study,” in Proc. ofMSR ’10, 2010, pp. 11–20.
[Nistor’13] A. Nistor, T. Jiang, and L. Tan, “Discovering, reporting, and fixing performance bugs,” in Proc. of MSR ’13, 2013, pp.
237–246.

Ambari'$$

A product bug is a bug that aﬀects thequality of software products.
n Security bug [Gegickʼ10 etc.]ex.
■ Authentication error
A bug that has security risks■ Session errorn Performance bug [Nistorʼ13]
ex.
A bug that makes systemʼs ■ Memory leak
■ Hung up
performance degraden Breakage bug [Shihabʼ11]
ex.
■ Regression error
A functional bug that was ■ “Ver.x is ﬁne, ver.(x+1)
doesnʼt work”
made by code modiﬁcations
to add new features or to ﬁxbugs

Our Dataset
BUG
IMPROVEMENT
871
129
580
420
734
26663
337

Manual Classiﬁcation: Results!High impact bugs%##$(#$##(##  

$$*$)

%$&#)

%'%

+%

&,(&)#Contact : masao@sys.wakayama-u.ac.jp