Defect / Bug Tracking tools
What are the different defect / bug tracking tools available in the market.
I have got to know about a few.
Are there any other similar tools that anyone knows?
I never tried it but FogBugz looks neat; otherwise wikipedia gives you a couple of links to lists.
There are hundreds of bug tracking tools available. A quick Google search ("bug tracking tool") will return most.
Originally Posted by Pushkar Joshi
You can find some here: https://en.wikipedia.org/wiki/Bug_tracking_system
And you can find some here: All Things Quality: Trial Versions of Commercial Bug Tracking Tools
Mantis is a good one for open source dev. But I tend to like Jira for it's large integratio eco system.
Something else to look at is general Task tracking system. Most bug trackers are really just task tracking but with labels changed to have 'bug' in the description.
Bugzilla,Lean,Mantis,Jira are the best tools for tracking bug or defects
Hi, I tried zipBoard (zipboard.co). It is great Bug tracking tool, it also gives visu
Hi, I tried zipBoard (zipboard.co). It is great Bug tracking tool, it gives visual feedback, rather than lines of text and you can also integrate your projects with JIRA.
I think these days if I were implementing a bug tracking system I'd probably use force.com for enterprises with over 1000 employees.
In this day and age, bug tracking is enough for most companies engineering department, you'll most likely need a full ALM solution to tie bug tracking with development and project planning. But there still is a large disconnect between business and engineering. C-level Management still doesn't see the direct connections between development projects and the rest of the company like sales, marketing, and finance. So you'll want to expose your development data to business systems so they can pull metrics and calculate ROI of bug fixes and engineering project before they shove a whole series new outrageous features down the pipeline.
My opinion is most bug tracking system sucks. For the most part the majority is basically a simple ticketing system with a state transitions and attachment functionality bolted on. Jira one of the most popular systems is at its core just a very limited ticketing tracking system. It's remarkable the amount of integration people have invested with Jira, but as a platform I do feel Jira is very limited in what it can do. If I wanted to create a Master Data Strategy with Jira, I'd probably have a lot of polling chron jobs that pull data, compare what changed, and use Jira APIs to make ticket modification. With force.com you get a barebones ticket and contacts management platform with event driven processes that is flexible. You can add custom apps and market place plugins for various business processes very easily and customize it to tailor your business. With it I can adapt it to bug tracking by adding a simple state transition workflow (open -> in development ->etc.. etc... -> Fixed -> deployed -> closed), tell it what data I want to publish as events, and any business process that wants that data can subscribe to it. Then I can easily put together dashboards and reports that give upper management more visibility into the state of engineering as a cool infographic.
What's really cool about having a bug system integrated with an enterprise system of this level, is you can pull some advanced analytics and decision support system you normally cannot do with a simple ALM alone. For example, being able to tie lost customers to specific bugs and measure ROI for fixing existing bugs. For new feature development, you can tie sales leads that mention a feature with the ticket for implementing the feature and see the ROI for implementing the new feature. You can query which contracts are associated with features and have transparency through out the organization to empower employees to see the big picture and set their own priorities.
Last edited by dlai; 05-27-2016 at 04:08 AM.