如何在Bug报告注释中进行讨论以缩短Bug修复时间?

2019 IEEE 19th International Conference on Software Quality, Reliability and Security (QRS) Pub Date : 2019-07-22 DOI:10.1109/QRS.2019.00044

Yuki Noyori, H. Washizaki, Y. Fukazawa, Keishi Oshima, Hideyuki Kanuka, Shuhei Nojiri, Ryosuke Tsuchiya

{"title":"如何在Bug报告注释中进行讨论以缩短Bug修复时间?","authors":"Yuki Noyori, H. Washizaki, Y. Fukazawa, Keishi Oshima, Hideyuki Kanuka, Shuhei Nojiri, Ryosuke Tsuchiya","doi":"10.1109/QRS.2019.00044","DOIUrl":null,"url":null,"abstract":"Bugs must be resolved efficiently for developers' limited resources. Bug reports are necessary for the bug modification process. Service user reports a bug as a bug report. Developer read bug reports and fix bugs. The developer can make discussion by posting comments on reported bug reports. There are several researches on the initial report of the bug report so that bugs can be fixed efficiently. But there are few researches on bug report comments. We focus on comments on bug reports. Currently, everyone is free to comment, but the modification time may be affected by how to comment. We investigate the topic of comments of the bug report. As a result of the investigation, the fact that the topics are mixed does not affect the modification time, however we found a tendency to shorten the modification time when the topic of the solution started early.","PeriodicalId":122665,"journal":{"name":"2019 IEEE 19th International Conference on Software Quality, Reliability and Security (QRS)","volume":"124 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2019-07-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"8","resultStr":"{\"title\":\"What are Good Discussions Within Bug Report Comments for Shortening Bug Fixing Time?\",\"authors\":\"Yuki Noyori, H. Washizaki, Y. Fukazawa, Keishi Oshima, Hideyuki Kanuka, Shuhei Nojiri, Ryosuke Tsuchiya\",\"doi\":\"10.1109/QRS.2019.00044\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Bugs must be resolved efficiently for developers' limited resources. Bug reports are necessary for the bug modification process. Service user reports a bug as a bug report. Developer read bug reports and fix bugs. The developer can make discussion by posting comments on reported bug reports. There are several researches on the initial report of the bug report so that bugs can be fixed efficiently. But there are few researches on bug report comments. We focus on comments on bug reports. Currently, everyone is free to comment, but the modification time may be affected by how to comment. We investigate the topic of comments of the bug report. As a result of the investigation, the fact that the topics are mixed does not affect the modification time, however we found a tendency to shorten the modification time when the topic of the solution started early.\",\"PeriodicalId\":122665,\"journal\":{\"name\":\"2019 IEEE 19th International Conference on Software Quality, Reliability and Security (QRS)\",\"volume\":\"124 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2019-07-22\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"8\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2019 IEEE 19th International Conference on Software Quality, Reliability and Security (QRS)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/QRS.2019.00044\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2019 IEEE 19th International Conference on Software Quality, Reliability and Security (QRS)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/QRS.2019.00044","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 8

摘要

由于开发人员的资源有限，必须有效地解决bug。Bug报告对于Bug修改过程是必要的。业务用户将bug报告为bug报告。开发人员阅读bug报告并修复bug。开发人员可以通过在报告的bug报告上发表评论来进行讨论。对bug报告的初始报告进行了多次研究，以便有效地修复bug。但是关于bug报告注释的研究很少。我们关注bug报告上的注释。目前，每个人都可以自由评论，但修改时间可能会受到如何评论的影响。我们调查了bug报告的注释主题。通过调查发现，题目混合并不影响修改时间，但我们发现，当解决方案的题目开始得较早时，修改时间有缩短的趋势。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

查看原文本刊更多论文

What are Good Discussions Within Bug Report Comments for Shortening Bug Fixing Time?

Bugs must be resolved efficiently for developers' limited resources. Bug reports are necessary for the bug modification process. Service user reports a bug as a bug report. Developer read bug reports and fix bugs. The developer can make discussion by posting comments on reported bug reports. There are several researches on the initial report of the bug report so that bugs can be fixed efficiently. But there are few researches on bug report comments. We focus on comments on bug reports. Currently, everyone is free to comment, but the modification time may be affected by how to comment. We investigate the topic of comments of the bug report. As a result of the investigation, the fact that the topics are mixed does not affect the modification time, however we found a tendency to shorten the modification time when the topic of the solution started early.

求助全文

通过发布文献求助，成功后即可免费获取论文全文。去求助

来源期刊

2019 IEEE 19th International Conference on Software Quality, Reliability and Security (QRS)

自引率

0.00%

发文量