@techreport{oai:ipsj.ixsq.nii.ac.jp:00163643,
 author = {Md., Rejaul Karim and Akinori, Ihara and Xin, Yang and Eunjong, Choi and Hajimu, Iida and Kenichi, Matsumoto and Md., Rejaul Karim and Akinori, Ihara and Xin, Yang and Eunjong, Choi and Hajimu, Iida and Kenichi, Matsumoto},
 issue = {9},
 month = {May},
 note = {Good quality bug reports are the primary means for developers to fix the bugs. However, the quality of the bug reports depends on the contents that help developers to resolve the bugs. This research aims to investigate what and how information is provided in the bug reports. Using high-impact bug reports of Apache Camel project, we conducted a case study. In details, we manually investigated high-impact bug reports to identify frequently reported features and how they affect on the bug fixing time. As a result, we found out frequently reported features set for each type of high-impact bugs. Moreover, no strong relationship exists between provided features and the bug fixing time., Good quality bug reports are the primary means for developers to fix the bugs. However, the quality of the bug reports depends on the contents that help developers to resolve the bugs. This research aims to investigate what and how information is provided in the bug reports. Using high-impact bug reports of Apache Camel project, we conducted a case study. In details, we manually investigated high-impact bug reports to identify frequently reported features and how they affect on the bug fixing time. As a result, we found out frequently reported features set for each type of high-impact bugs. Moreover, no strong relationship exists between provided features and the bug fixing time.},
 title = {Improving the High-Impact Bug Reports: A Case Study of Apache Projects},
 year = {2016}
}