Mapping Bug Reports to Relevant Developers
Ayesha Khan1, Gudapati Syam Prasad2
1Ayesha Khan, Department of CSE, Koneru Lakshmaiah Education Foundation, Vaddeswaram (A.P), India.
2Dr. Gudapati Syam Prasad, Department of CSE, Koneru Lakshmaiah Education Foundation, Vaddeswaram (A.P), India.
Manuscript received on 07 March 2019 | Revised Manuscript received on 20 March 2019 | Manuscript published on 30 March 2019 | PP: 683-689 | Volume-8 Issue-5, March 2019 | Retrieval Number: E3323038519/19©BEIESP
Open Access | Ethics and Policies | Cite | Mendeley | Indexing and Abstracting
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC-BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/)
Abstract: Every time a bug reportis newly generated, developers are always required to recreate the bug, execute code and performa nalysis to know the cause, this process is laborious and time absorbing. A tool which maps the bug reports to their relevant developers, preserving how the bug is solved and analyzing how many bugs are solved till date can deprecate the time absorbing to analyze bugs. This paper introduces an adjustable mapping approach where bugs with triage can be assigned to the developers who have experience in solving that particular type of bug and once the bug is solved the solution, status of the bug can be preserved in the bug repository. Based on the preserved values, we use the instance selection approach to find the number of bugs solved under a particular time period using time stamp and analyze the intensity of the bugs in the form of employee analysis and performance analysis. We also introduce community support where the developers can raise the questions with respect to bugs.
Keyword: Mapping Bug Reports, Bug Triage, Bug Repository, Timestamp, Bug Analysis.
Scope of the Article: Predictive Analysis