Bug tracking is the process you use to address programming errors found. This process includes recording the bug, reviewing it, recording the fix needed, and deciding whether or not the bug will be fixed considering budget and schedule. [Source]
A bug 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 sort of issue tracking system. [Wikipedia]
Below table shows important features of different Bug Tracking Tools or Issue Tracking Tools .
For OS, Price and Support see here.
| S.No. | Name | Features |
|---|---|---|
| 1. | Bugzilla | 1. Advanced Search Capabilities. 2. Email Notifications Controlled By User Preferences. 3. Bug Lists in Multiple Formats (Atom, iCal, etc.). 4. Scheduled Reports (Daily, Weekly, Hourly, etc.) by Email. 5. Reports and Charts. 6. Excellent Security. |
| 2. | BestPractical | 1. Dashboards and Relationship Graphs. 2. Rich-text Editing. 3. Time Tracking and Reporting. 4. Integration with your existing User Login system. 5. A self-service interface for non-users to interact with their tickets. |
| 3. | AdminiTrack | 1. Proven track record - serving subscribers in over 25 countries since 2001. 2. Track and view issues across multiple projects - link any user to any project. 3. Define your own custom fields. 4. Easy to learn and use - online help provided. 5. Very fast - even for low-bandwidth connections. 6. Free support and version upgrades - no software installation required. |
| 4. | Borderwave | 1. Quickly create defects/feature/suggestions by product and version. 2. Unlimited number of products and versions for each product. 3. Employees can easily find out what work is left to be done on a product and version. 4. Custom terminology so the software fits your business model. 5. Audit Trail accurately tracks additions, modifications and deletions in the database. 6. Manager Summary - At login, project managers are given a summary of their project statuses. |
| 5. | BugAware | 1. Enterprise Wide Access 2. Highly Customizable 3. Multi-Lingual 4. File Attachments 5. Dynamic Reporting 6. Advanced Searching 7. Custom Fields 8. Role based security |
| 6. | Bugtrack | 1. 24/7 Web access from anywhere in the world through a standard Web browser. 2. Secured with SSL encryption. 3. RSS feeds. Subscribe to updates via RSS 2.0. 4. Time Estimation. Track estimated time and the actual time to resolve a bug. 5. Role-based permissions. Manage user roles and access for each project. 6. Easy bug addition, using rich text with editing and spellchecking tools. |
| 7. | Bughost | 1. Defects per project 2. User Licenses 3. Project Licenses 4. Defect Retention 5. Audit Trail 6. SSL Secure Forms 7. Custom Reports 8. Export to CSV 9. Export to XML 10. Statistics Reports |
| 8. | Bugcentral | 1. Query database through lookup tables to track severity, operating system, category, version, browser, test case, priority, and module. 2. Review bug history and audit log. 3. Auto-notification to managers and quality assurance teams when status changes. 4. Set group and user-level security for each menu and field. 5. Set fields and menus as hidden, read-only, or editable. 6. State-of-the-art firewall security. |
| 9. | Bugimpact | 1. Unlimited : projects, entries/bugs/issues, and attachments storage space. 2. History : record's discussion thread may contain as many comments as you need. Details size is unlimited. All comments are saved and logged in the bug tracking system. 3. Project management : Ability to add components, Requirements and test cases to the project. We keep History if Requirements and test cases are changed. 4. Hierarchical area : to better categorize where the bug/issue belongs. 5. Link : related bugs may be linked. 6. Role-based permission : ability to manage user roles. |
| 10. | Bug-track | 1. Easy to use Dashboard. 2. Context sensitive help. 3. Complete tracking features including: versions, components, operating systems, history etc. 4. Linked bugs function allowing the creation of relationships between bugs/tasks. 5. Copy bug function from one project to another. 6. Saved user queries per project. |
| 11. | Websina | 1. Bi-directional relationships between projects, for example, a bug report can be linked to a test case entry in Test Case. 2. Works in any languages using UTF-8, including Chinese, Japanese, and Korean. 3. Support direct screen capture for attachment (available as add-on). 4. Configurable email notification triggers or listeners (per project, per user). 5. Metrics reports, advanced search, and re-usable stored queries. |
| 12. | CENSUS | 1. Nothing to install on client machines. 2. 24x7 access from any computer. 3. Easy to deploy, setup, and administer. 4. Tight integration with Microsoft Visual SourceSafe. 5. Provides Web-based, distributed access to VSS projects. 6. Send e-mail notifications whenever a Bug Tracker issue is updated. |
| 13. | FogBugz | 1. Infinitely customizable. 2. You can use Filters to sort, search, slice, and dice based on any criteria you want. 3. You can add, remove, rearrange, and size columns to show the exact report you want to see. 4. FogBugz filters can be saved, named, and shared with your entire team. |
| 14. | Fastbugtrack | 1. 5 Minute Installation. 2. Increase productivity. 3. Improve workflow. 4. A Proven Track Record. 5. Minute Installation. 6. Easy-To-Use. |
| 15. | Atlassian | 1. Create new bugs in seconds from your browser, email, IDE or smartphone client. 2. Navigate JIRA menus and execute frequently used actions using keyboard shortcuts. 3. View activity history to access recently opened issues, projects and searches. 4. Use Quick Search to find bugs based on user, project, issue key or filter shortcuts. 5. Activity streams display recent changes across bugs, issues, projects or people. |
| 16. | Jtrac | 1. Extremely easy to install. 2. Unlimited project spaces per installation. 3. Custom fields and drop-downs for each project. 4. Customizable workflow per project. 5. Field-level permissions. 6. Translated into multiple languages. 7. Support for LDAP, Active Directory or CAS based authentication. |
| 17. | Mantisbt | 1. Simple User Experience. 2. Email notifications. 3. Customizable Issue Pages. 4. Multiple Projects per instance. 5. Support for Projects, Sub-Projects, and Categories. 6. Available in 68 localizations. 7. Built-in Reporting (reports / graphs). |
| 18. | Ozibug | 1. Audit trails. 2. File Attachments. 3. Multiple Module Support. 4. Email Notifications. 5. Custom Reports and RSS feeds. 6. System Statistics. 7. XML data storage. |
| 19. | Problemtracker | 1. Easy to use and deploy. 2. Provide full access from any platform, anywhere. 3. No client-side installation. 4. Works well with multi-national products & organizations. 5. Easier to use and less error prone for multi-location deployment. 6. Leverage standard databases and tools. 7. Automate escalation of problem areas to ensure timely resolution. 8. Virtually limitless expansion as your user-base grows. |
| 20. | Squishlist | 1. Easily add, modify, or remove fields. 2. View the entire history of an issue, including all comments, attachments, and field changes. 3. Perform advanced user-defined searches. 4. Save or share searches to continuously monitor changes. 5. Generate custom statistics about project issues. 6. Watch issues or custom searches so you can easily track changes from your project home page or through automatic emails. |
| 21. | Projectlocker | 1. Full-Text Searches: Find tickets, code changes, and Wiki pages by keyword search. 2. Create Tickets from Email: Let your team, partners, and customers file new tickets in Trac using E-mail. 3. Customize fields: Instantly add custom fields to your Trac. 4. Web-based trac-admin: Manage your components, milestones, and other settings using a simple Web-based UI. 5. Web-based trac.ini Management: Customize your Trac settings. |
| 22. | Teamatic | 1. Create, edit and deactivate users. 2. Create, edit and deactivate projects. 3. Customize your search criteria. 4. Define up to five additional fields in the case detail form. 5. Define up to four different Case Types for each project. 6. Backup your own data in XML format. |
| 23. | Trackstudio | 1. Fully configurable workflows. 2. Hierarchical task tree. 3. Multi-role support. 4. High usability. 5. Fast and scaleable design. 6. Database and O/S independence. |
| 24. | Visionproject | 1. Manage projects. 2. Manage issue. 3. Manage versions. 4. Manage time/cost. 5. Share document. 6. Search and filter. 7. Alerts/Escalations. 8. KB and Forum. 9. Access control. 10. Customizations. 11. Reports. |
| 25. | yKap | 1. Create and track bugs/defects. 2. Assign built-in or custom values for defect status, priority, complexity. 3. Assign Project/Module for the defect. 4. Optionally enter a preferred closing date. 5. View the complete history of a defect. 6. Exhaustive customization. |
| 26. | Prtracker | 1. Create multiple projects where each project has its own data entry and workflow configuration. 2. Restrict access to projects by PR-Tracker username and network login name. 3. Specify permitted operations for each username on a project by project basis. 4. Create and save powerful queries using AND, OR and NOT operators and wildcard text search. 5. Create and save multiple views of problem report lists sorted anyway you want. |
| 27. | Unfuddle | 1. Unfuddle provides a complete solution for bug tracking via a robust ticket system. With Unfuddle's free bug tracking features it is easy to create tickets, track progress, and keep your customers happy. 2. Unfuddle is a secure, hosted software development environment and project management solution for small software development teams. 3. Unfuddle tickets help your project to stay organized. Prioritize, comment upon and then assign your tickets to your team members. With time tracking you can even keep track of which team members have been working on the tickets for the project. 4.Every ticket benefits from workflow management and a verbose audit trail so you can keep track of who made certain changes for a ticket and when these changes were made. |
| 28. | Codebeamer | 1. Highly customizable standard and custom issue fields. 2. Configurable tracker workflows. 3. Comments and attachments. 4. Associations to other issues, wiki pages, documents or source code. 5. Audit trail. 6. Cut / copy / paste / duplicate / move issues between trackers and projects. 7. Mass editing. 8. Versioning. 9. Locking. 10. Access and audit trail. 11. Full text search on MS-Word, RTF, PDF, HTML, Wiki and text documents. |
| 29. | Flyspray | 1. Multiple database support, currently MySQL and PGSQL 2. Easy installation 3. Easy to use 4. Multiple projects 5. 'Watching' tasks, with notification of changes (email or Jabber) 6. Comprehensive task history 7. File attachments. 8. CSS themes. 9. Dependency graphs. |
| 30. | Fossil | 1. A bug-report in fossil is called a "ticket". Tickets are tracked separately from code check-ins. 2. Every ticket change artifact contains (among other things) A. a timestamp, B. a ticket ID, and C. one or more name/value pairs. The current state of a ticket is found by replaying all ticket change artifacts with the same ticket ID in timestamp order. For a given ticket, all values are initially NULL. As each ticket change artifact is encountered, values are either replaced or appended, according to a flag on the name/value pair. The current values for the fields of a ticket are the values that remain at the end of the replay process. 3. To create a new ticket, one inserts a ticket change artifact with a new ID. The ticket ID is a random 40-character lower-case hexadecimal number. The "tktnew" page in the fossil web interface creates new ticket IDs using a good source of randomness to insure uniqueness. The name/value pairs on the initial ticket change artifact are the initial values for the fields in the ticket. 4. Amending a ticket means simply creating a new artifact with the same ticket ID and with name/value pairs for those fields which are changing. Fields of the ticket which are not being modified should not appear as name/value pairs in the new artifact. 5. This approach to storing ticket state means that independently entered changes are automatically merged together when artifacts are shared between repositories. Tickets do not branch. This approach also makes it trivial to track the historic progression of changes to a ticket. |
| 31. | Countersoft | 1. Grouping related projects by department, line-of-business, clients helps encourage user participation. Break down each project into hierarchical components and versions to ensure bugs end up in the right place. Slice and dice your bugs any way you like and save common project filters 2. Issues drive projects so make them simple to create, easy to view, and flexible to manage. 3. Workflow should help you control who can do what and when. But you also need to control who can see what and when. Set up workflows and apply them to your bug tracking projects. For even more granular control define workflows at the Issue Type level to help you control how different business processes should start and finish. 4. Automatic Project Road Maps and Change Logs provide forward-looking and historic views of what is coming up and what was done. |
| 32. | Elsitech | 1. Users can define an unlimited number of object properties, item types, and relationships. 2. IssueNet’s web service architecture allows access to both a rich client and browser based interface over the internet, via ClickOnce Technology. It permits administrators to deploy and update the software from a single location. 3. IssueNet has an extensive integration with email clients, including Microsoft Outlook. 4. Tasks are automatically created and assigned during the workflow execution. 5. Model and organize business processes into distinct workflows and tasks. 5. Scalability is crucial. As such, IssueNet allows for multiple and nested workflows associated with any issue type. 6. SimpleKnowledge Capture interface allows team to quickly create a formatted and categorized Knowledge Base article and make this available to other users via IssueNet client and web portal. |
| 33. | Redmine | 1.Multiple projects support. 2. Flexible role based access control. 3. Flexible issue tracking system. 4. Gantt chart and calendar. 5. News, documents & files management. 6. Feeds & email notifications. 7. Per project wiki. 8. Per project forums. 9. Time tracking. |
| 34. | Trac | 1. Trac is a lightweight project management tool that is implemented as a web-based application, written in the Python programming language. It emphasizes ease of use and low ceremony, and is open source. 2. As it's open source, if it doesn't quite fit your needs, you can always make changes yourself, write plugins, or commission someone else to do so. 3. Track the progress of resolving individual bugs, issues, feature requests, and ideas - each with its own ticket (numbered, as in a waiting room queue system). 4. Trac gives you a number of convenient ways to stay on top of events and changes within a project. You can set milestones, and view a roadmap of progress towards them (as well as historical achievements) in summary. 5. Trac has a simple permission system to control what users can and can't access. |
| 35. | Seapine | 1. Support distributed teams with centralized and automated issue management. 2. Use TestTrack Pro Web or the cross-platform TestTrack Pro. Client to access projects and issues. 3. Attach files to issues and view them in TestTrack Pro. 4. Integrate with popular IDEs, including Microsoft Visual Studio .NET, using the TestTrack add-in. 5. Easy Installation and Maintenance. 6. Perform a complete installation in minutes. 7. Configure and maintain TestTrack Pro using a cross-platform. 8. GUI client or a Web-based client. |
| 36. | Getdonedone | 1. Open, In Progress, Not reproducible, Missing information, Ready for retest... Most issue trackers treat these statuses as just another "tag". But, they're much more than that. 2. Issue statuses have meaning. If someone needs more information on an issue you've assigned, it should be obvious. DoneDone issue pages make it clear what has to happen next and who's responsible for it. 3. Most issue tracking tools don't tell you what's new or updated. You're left having to sift through a laundry list of updates, comments, and status changes to figure out what you haven't seen yet. 4. DoneDone keeps track of all this for you. All new issues are highlighted in blue with an icon. All updated issues are highlighted in blue. We also highlight updates in an issue history that you haven't seen yet. |
| 37. | Tbitsglobal | 1. Configurable workflow and Business Rules: Model and enforce your company's existing process. Automatically route issues around to get them resolved. Improve productivity and quality. 2. Automatic Notifications and Reminders: Configurable email notification; separate rules and settings for each various types of Issues to be tracked. Automatically notify appropriate users on change of assignment, change of state, etc. 3. Alerts and Escalations: Time-based alerts for each issue, as reminders or escalations if the issue is not taken care of by the specified date & time. (In addition to the event-based email notification described above). 4. Advanced Search: Freely define report queries based on any value of any field. Use AND, OR, NOT operators to define complex queries. Save queries for quick access to information in the future. Design and save report formats. Obtain summary reports for high-level views of the status of each user and every product in the Tracker database. 5. Email Integration: Submit an Issue to Expediter by simply emailing, to take an action on an issue all a user will have to do is reply to the email for the Issue which he receives. |
| 38. | Trackplus | 1. Manage all types of projects. 2. Manage all types of issues and artifacts. 3. Monitor project progress. 4. Manage budgets and expenses. 5. Support your custom workflows. 6. All reports are based on issue filters. 7. Filters can be stored and reused. |
| 39. | Sifter | 1. Sifter lets you organize issues by project with a focus on status and accountability. Everything is designed from the ground up to help team members focus on their issues. 2. Creating an issue is quick and concise. Once they're created, everything is color-coded and important details are only a glance away. 3. Quickly and easily update issue statuses with a comment. Sifter always knows which options are relevant based on the current status. 4. We all work differently. Sifter lets you filter your issue list so you can work through your issues your way. |
| 40. | Hedgehoglab | 1. Track anything: You can track everything from bugs, features, requirements, tasks and incidents. 2. Search & Filtering: Powerful full-text search enabled with filtering capabilities that allow you to view only the information you need. 3. Email: Geared towards preventing notification spam and enabling you to keep informed. 4. Reporting: Activity streams, time reports, change history and release notes to enable intelligent reporting. 5. Mobile compatible: fixx comes with an enhanced mobile web experience for your phone. |
| 41. | Bug Genie | 1. Reporting an issue takes place on one page - no need to click through several pages. Because we use Web 2.0 technology to update the content as the issue is created, information presented is relevant to the user at all times. 2. A sidebar presents the user with helpful information - such as how to write a good issue description - making sure the user is never lost. The same sidebar also provides information about other similar issues, reducing the chance for duplicate issue reports. 3. Easy to use and administer. There are no configuration files. No, seriously. Administer anything from our Configuration center, and it's updated instantly. |