IJERT-Online Bug Tracking System on the Web (original) (raw)
Related papers
Effective Bug Tracking Systems: Theories and Implementation
IOSR Journal of Computer Engineering, 2012
Bug tracking is an essential discipline in the domain of software engineering. It has far reaching effects on the system when effectively used. The information provided in terms of bugs and solutions in the bug reports can help software engineers to act on them quickly and ensure that they are either rectified or eliminated from the system. The bulk of information provided in the bug reports may cause problem to developers in ascertaining poorly designed information. Therefore the bug tracking systems are to be improved and follow certain standards. To overcome the problem, we propose four fundamental directions to enhancing effectiveness of bug tracking systems. To demonstrate the efficiency of the proposed directions, we develop a prototype application that tracks bugs effectively by capturing essential information from users and help resolve bugs quickly. I.
Web-based issue tracking for large software projects
IEEE Internet Computing, 1998
Many problems are found and fixed during the development of a software system. The Project Issue Tracking System toolkit, a Web-based issuemanagement tool, can be used to organize issue reports during development and to communicate with different project teams around the world.
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.
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
International Journal for Research in Applied Science and Engineering Technology Ijraset, 2020
System of Monitoring Bugs is a software application that can be accessed through out an organization .It is an web based code which runs on web portal. A bug might be in design or in basic code large amount of bugs might be in system development. It is not that easy to manage bugs in simple word documents or keeping the whole thing in brain so in order to keep track of software bugs in their work, a major component of System of Monitoring Bugs is database. As System of Monitoring Bugs is written uses java servlets and java scripting language which works with prerequisites MySQL database and webserver ,it can be installed on different operating system such as Windows and Linux. Every bug its related changes are systematically recorded in web based system So the application is more scalable. This method is handled with security measures like granting admittance only to specified groups and permitting authorized members to modify the process .
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.
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.
Change and Bug Tracking System: Anjung Penchala Sdn. Bhd.
Change, 2010
Defects or bugs have been existed as a problem in the system and they are normally inevitable in software development. Most software bugs arise from mistakes and errors made by people in either a program's source code or its technical design. Huge amount of bugs could be found in system development. It was relatively difficult to manage bugs in simple word documents or remember everything in one's head. Thus Change and Bug Tracking (CBT) System has been introduced in order to keep track of the reported bug in the system. By using this tracking system, every user can report and follow up the issue in the system. This system provided a platform for users from different departments to report issues and understand the latest progress in a product. It consolidated and organized information in single system and centralized data repository for the changes and bugs in system. Besides, this system could be accessed by team members concurrently to improve efficiency and they can search particular information in the system easily. It made communication between teams more effective and all the bugs and changes are recorded in web based system and hence the system is scalable.
IJERT-Implementation Of Effective Defect Tracking System In Software Egineering
International Journal of Engineering Research and Technology (IJERT), 2012
https://www.ijert.org/implementation-of-effective-defect-tracking-system-in-software-egineering https://www.ijert.org/research/implementation-of-effective-defect-tracking-system-in-software-egineering-IJERTV1IS8683.pdf Defect Tracking Systems in testing is the process which report the defects and also provides the complete information regarding defects. In the testing phase the tester will identify the defects. Whenever the tester encounter number of defects he adds the defect id and information in the database.The tester reports to both project manager and developer. The defect details in the database table are accessible to both project manager and developer. The project manager assigns projects to the developers. The developer develops the projects as per customer requirements. The project manager itself assigns the developed applications to the Testers for testing. The tester tests the application and identify the defects in the application. When the tester encounter number of defects, he generates a unique id number for each individual defect. The defect information along with its id are mailed to the project manager and developer. This is defect Report. These are stored in the database. This is useful for further reference. Defect information includes the defect id, defect name, defect priority, project name, defect location, defect type.This whole process continues until all the defects are got fixed in the application.The defect report is mailed to the project manager and the developer as soon as the defect is identified. This makes that no error will go unfixed because of poor communication. It makes ensure that anyone who needs to know about a defect can learn of it soon after it is reported. Defect Tracking System plays an vital role in the testing phase. But it supports assigning projects for the developer, tester by the project manager. The Defect Tracking System maintains the different users separately i.e., it provides separate environments for project manager, developer and tester.
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.