26-04-2012, 10:31 AM
ISSUE TRACKER
ABSTRACT:
A bug tracking system or issue tracking system is a software application that is designed to help quality assurance and programmers keep track of reported software bugs in their work. It may be regarded as a type of issue tracking system. Many bug-tracking systems, such as those used by most open source software projects, allow users to enter bug reports directly. Other systems are used only internally in a company or organization doing software development. Typically bug tracking systems are integrated with other software project management applications. Having a bug tracking system is extremely valuable in software development, and they are used extensively by companies developing software products. Consistent use of a bug or issue tracking system is considered one of the "Hallmarks of a good software team”. Main features Multiple projects support Manage all your projects with one E-Issue Tracker instance Each user can have a different role on each project Each project can be declared as public (visible by anyone) or private (visible by project members only)Modules (e.g. wiki, repository, issue tracking, ...) can be enabled/disabled at project level Flexible issue tracking system Define you own statuses and issue types Workflow transitions can be set up for each issue type and role through the web-based administration interface (a default configuration can be loaded when installing the application)Gantt chart and calendar Automatic gantt and calendar based on issues start and due dates.
EXISTING SYSTEM:
The existing system is Users who are using the software will report the bugs which are occurred on running of it they will send an e-mail to the company and report about bug. Another way of finding the software bugs is the software testers who work on the project will find out the bugs which are occurred while developing the code. In this way they will rectify the issues related to Bugs.
LIMITATIONS OF EXISTING SYSTEM:
• The users who are using the software will report to the developers in their own way. But in reality are the developers can catch the expectations of the customer and try to rectify it. If they fail so then it will be a remark to the reputation of the company.
• Software Testers who find out the bugs will report to the Quality Management they will review in a formal meeting and the developer has to take an action on the bug occurred which will degrade the software performance. But how far the developer will rectify the Bug and maintain good quality when total code is developed.
PROPOSED SYSTEM:
By using the e-issue tracker functionality of Time tracking is there so Time can be entered at project or ticket level Simple report to view time per user, issue type, category or activity Custom fields You can define your own custom fields for issues, time-entries, projects and users Different formats are available: text, date, Boolean, integers, drop-down lists and checkboxes Custom fields can be displayed on the issue list and used as filters just like regular fields News, documents & files management You can easily post messages and share files Per project wiki and forums Wiki uses textile syntax and free linking within the wiki using brackets. Difference and annotate views are available in Repository browser and different Existing repositories can be attached to each of your projects lets you browse their contents, view and search change sets Difference and annotate view User self-registration support Optionally, you can allow users to register online 3 account activation methods are available: automatic (no confirmation required), manual (by administrators) or through an auto generated URL sent via email
BENEFITS:
• Improve communication and team work in organization during exception
• Gain enterprise wide visibility into the status of issues across the various departments and functional areas
• Expedite the process of issue recording, review approval and finally closure as if automatically moves from one stage to other.
CONCLUSION
By using the e-issue tracker we can track the bugs in day to day programming thereby improving the quality of software. The consistent use of a bug or issue tracking system is considered one of the "hallmarks of a good software team”. Each project each project can be declared as public visible by anyone or private visible by project members only. Modules e.g. wiki, repository, issue tracking, can be enabled/disabled at project level Flexible issue tracking system