Effective Bug Tracking Systems: Theories and Implementation (original) (raw)
Related papers
BugTracking: A Tool to Assist in the Identification of Bug Reports
Open Source Systems: Integrating Communities, 2016
Issue tracking systems are used, in most software projects, but in particular in almost all free open source software, to record many different kinds of issues: bug reports, feature requests, maintenance tickets and even design discussions. Identifying which of those issues are bug reports is not a trivial task. When researchers want to conduct studies on the bug reports, managed by a software development project, first of all they need to perform this identification. The job for researchers here is very different from the bug triaging that researchers do. In the latter case, people with a considerate experience in the project make a decision based on the information available at that time (maybe just a short comment by some user), asking, if needed, for more details. In the former case, researchers usually have not that experience in the project, but they have at their use all the information produced, until the moment the issue was closed. This may include not only all comments and actions on the issue tracking system, but for example, discussions about a fix in the code review system, or the final fixing patch in the source code management system. Having all that information conveyed to the researchers, in an easy, flexible and quick way, accelerates and makes their decision process much more reliable. It simplifies large scale manual analysis of issues (in hundreds or thousands), helping researchers to ensure that they are really working with what they intend to work: bug reports. This paper presents a tool designed to solve exactly the problem of providing the researchers with all the relevant information needed to decide whether an issue corresponds to a bug report or not. The tool uses information extracted automatically from the projects repositories. It offers a web-based interface which allows collaboration, traceability and transparency of the identification of bug reports. All this makes the process easier, faster, and more reliable.
Bug Tracking, Help Desk Ticketing, issue raising, search facility, help information, issue resolution. Issues related to software projects can be raised, tracked and resolved by Employees of different departments. Resolved issues can be allowed to access from Knowledge Base as Knowledge elements. The different groups and representatives can interact each other through emails. The issue tracking system does all the jobs that are done in conventional system but ,here , everything is done in more formal and efficient manner. All the users of organization can interact with each other through the Issue Tracking System. This system acts as an interface between the employees thereby enabling them to forward their issues to the centralized Issue tracking system. Hence, making the work easy for both the issue raiser and the resolved. It totally avoids the involvement of middlemen in getting resolution for a particular issue.The Issue Tracking system is an intranet application, which provides information about issues in software projects, in detail. This product develops a system that can be used by all the departments of a software organization. In the conventional method, all the issues are dealt manually .The progress of the issues are also checked in person, which is a tedious task. Here, in Issue Tracking, it fulfills different requirements of administrator and employees of a software development organization efficiently. The specific purpose of the system is to gather and resolve issues that arise in different projects handled by the organization
Evaluating a Tool for Bug-report Analysis and Search
lbd.dcc.ufmg.br
Bug report tracking systems have been used to facilitate the maintenance and evolution of software. However, duplicate entries of bug reports in such systems can considerably impact productivity within software project. This reduction in productivity occurs because duplicate entries demand more time for search and analysis of bug reports. In this context, this paper presents the main problems caused by bug report duplication problem. In addition, a tool for bug reports search and analysis (BAST) is proposed to deal with the duplication avoidance, as well as, it also presents a case study to evaluate the tool. For the evaluation, we compared BAST against a baseline tool in a private company for software testing. The results showed that BAST worked better than the other one, both to reduce the time of analysis, as well as, to reduce the number of duplicates submitted.
Improving Software Quality Assurance Using Bug Tracking System
—This paper entitled Improving Software Quality Assurance Using Bug Tracking System is mainly for applications developed in a company to keep track of employee skills and based on the skills assigning of the task is done to an employee and aims at creation of a Bug Tracking System for enhancing the software quality. This project will be accessible to all developers and its facility allows developers to focus on creating the database schema and while letting the application server define table based on the fields in JSP and relationships between them. Improving Software Quality Assurance Using Bug Tracking System is an automated system that can be useful to employees and the managers in any functional organization. This Bug Tracking System gives the facility to define the tasks in the organization and also allows the managers to track the bugs spent by the employee for that particular task. A report generation facility is supported in BTS (Bug Tracking System) that allows the managers to analyse which those skills by employee are utilized and those which are not utilized. This tool can help managers for Bug estimation per project or application. This tool helps employees to document their Bugs and analyse.
Does your Bug Tracking tool suit your needs? A Study on Open Source Bug Tracking tools
2017
Bug tracking tools are vital for managing bugs in any open source as well as proprietary commercial projects. Considering the significance of using an appropriate bug tracking tool, we assess the features offered by 31 open source bug tracking tools and their significance of usage in open source projects. We have categorized these tools into different classes based on their features. We have also conducted a developer survey by working with open source software practitioners to understand the effectiveness of these tools in their day-today software development. We also explored StackOverFlow-a developer Q&A forum to understand the developer experiences and challenges while using open source bug tracking tools. Our observations generated encouraging results that can used as a recommendation guide for open source software community to choose the best bug tracking tool based on their functional needs. Additionally, we have identified few features that are needed but not offered by most of these bug tracking tools.
BAST - A Tool for Bug Report Analysis and Search
2009
Bug tracker systems have been used to facilitate maintenance and evolution of software. However, duplicate entries of bug reports in such systems impact on the development productivity. It happens mainly because developers must carefully analyze incoming bug reports to check their validity, which some can take more than 20 minutes to be analyzed. In this sense, this work presents a tool for bug reports search and analysis, in order to improve such tasks.
Issue Tracking Systems: What Developers Want and Use
Proceedings of the 13th International Conference on Software Technologies
An Issue Tracking System (ITS) allows a developer to keep track of, prioritize, and assign multitudes of bugs, feature requests, and other development tasks such as testing. Despite ITSs play a significant role in day-today developers' activities, no previous study investigated what developers want and use in an ITS. The aim of this paper is twofold. First, we provide a feature matrix that maps six of the most used ITS to features, and second, we measure the developers' level of use and perceived importance of each feature. This knowledge has multiple benefits such as supporting the decision of the ITS to use and revealing promising areas of research and development. Specifically, quality improvement effort should target improving functionality in use, and development effort should target supporting functionalities needed. In this paper, we define and extract ten core ITS features and asked more than a hundred developers to rate their importance and use. Our results show that Advanced Search and Flexible Notifications are the most important features. Moreover, results show that no feature has been used by more than 90% of the respondents. Another interesting finding is that 27% of respondents rate Workflow Automation as a useful or required feature, despite having never used it themselves; this suggests the need to better training, exposure or of availability of ITS features. In conclusion, our results pave the way to significant research and development effort on ITS.
Bug tracking applications are majorly regular bugs which uses tools to tracks the bug from user through software development lifecycle to maintain the reliability and consistency. And just then the software system has any oversized user base, that is common in practice and different users may experience the same bug generation that may lead to many duplicacy in the bug report. The presence of redundant bug report hence finally ends up with many unnecessary attempts of designer lay out on detecting the same defects. To accelerate bug fixing task and store the price of inventor there is a huge demand for automated detection of redundant bug records. In that time, the proposed system explores the employment robust deep study technique as well as word embedding and convolution neural network to compute similitude between a set of bug reports and hence identify feasible redundancy. In contrast to the earlier process that is consider only common letters in the bug depiction for lexical similitude calculation. Here the main approach in an edge to push capture semantic logical similitude between the words. In that cases we are not improve conventional CNN models through merging few domain specific functions pull out from the bug records. Experimental results of the bug report show that CNN has made a significant advancement into duplicate detection accuracy above the conventional approach.
IJERT-Online Bug Tracking System on the Web
International Journal of Engineering Research and Technology (IJERT), 2013
https://www.ijert.org/online-bug-tracking-system-on-the-web https://www.ijert.org/research/online-bug-tracking-system-on-the-web-IJERTV2IS90595.pdf Online Bug Tracking System on the Web is a web-based code bug tracking system which runs on the web portal. It is a open source package which is written in the PHP scripting language and it works with the prerequisites MySQL Database, Microsoft SQL Database and PostgreSQL databases and the webserver. It can be installed on the different operating system such as Windows and Linux. Almost all the web browsers will be able to work as a client for tracking system. The Bug Tracking system generates the quick links to the auto generated individual searches such as like open issues, various Milestone to do-list, Most non-voted issues and the Project wish list for all the different projects in a tracking system. These all the quick searches can also be easily accessed from the different Issues in the system and whenever users or developers in the project space of the bug tracking system. It is the intelligent search that lets you to specify the number of every code debugged in seconds for finding the most recent issues in real-time. The bug tracking system can easily debug the project codes in online user interface on the web. It is open source and easier for developers to work on it.
An Initial Study on the Bug Report Duplication Problem
… (CSMR), 2010 14th …, 2010
According to recent work, duplicate bug report entries in bug tracking systems impact negatively on software maintenance and evolution productivity due to, among other factors, the increased time spent on report analysis and validation, what in some cases take over 20 minutes. Therefore, a considerable amount of time is lost mainly with duplicate bug report analysis. This work presents an initial characterization study using data from bug trackers from private and open source projects, in order to understand the possible factors that cause bug report duplication and its impact on software development.