BUGVILLA: Calibrating Bug Reports with Correlated Developers, Tracking Bug Reports, and Performance Analysis

A bug is defined as the error in code because of which a system cannot produce the desired output. Whenever a bug occurs, a bug report is created. To find the cause of a bug, developers will execute the whole code continuously and analyze the code depending upon the report they received. So the bug reports should be accurate as the developers depend on the bug report received to solve a particular bug. Bug reports are the documents which provide total information of a particular bug with different accuracy. We need to manage the bugs which arise while working on a software project. Developers usually take the help of spreadsheets and fill them with new bugs which are raised. But when the list of bugs increases to a large number and all developers working on a single spreadsheet to update bugs may create ambiguity. Every software project reaches this point, especially during testing and deployment when users tend to find an application’s bugs. So, a tool for tracking bug reports will be useful instead of a spreadsheet. Where tracking bug reports is an important feature which helps to observe the activities of software developers. Moreover, it is important to observe that a bug will be assigned to the developer who is an expert in solving that particular type of developer. This paper introduces a new tool for tracking bug reports, using which we can assign bugs to their respective developers, view bug status, check bug history, check the total performance of developers, and also communicate with developers by means of a group chat.