What is your bug/task tracking tool?This is a placeholder for overviews of bug/task tracking systems.
What i want to do here is:
Please put each tool in separate answer and please make it community owned wiki to give an option to add/edit to as many people as possible.
What is your tool for version control (FAQ) [1]
Free/Cheap Task/Bug Management software [2]
What bug tracking software do you use? [3]
Trac (http://trac.edgewall.org/)
It's sleek, fast, free and has subversion integration.
In another answer, reefnet_alex said about it: The browse source is excellent and having a Wiki built in is pretty useful. It's lightweight and easily customizable. On the down side, it's jack of all trades master of none.
Check out Redmine [1]. It has the look and feel of Trac plus
We use JIRA [1], which also has a great Eclipse plugin [2]
[1] http://www.atlassian.com/software/jira/I've used the open source Mantis Bug Tracker [1] for a medium-sized project, and although it didn't have many source-control integration features, the hability to handle custom fields, the workflow and reporting features worked awesome with my team.
And it's very clean code IMHO. Shouldn't be very difficult to extend and add/modify features.
It is easily integrated with Eclipse with the Mylyn-Mantis connector [2]
Bugzilla [1]
Features:
Plus:
Minus:
Links:
We use OnTime [1] which is a great tool and has both web and Windows clients, Visual Studio integration, accompanying web services, a customer facing portal, workflow support (which is essential to a good defect tool) and a lot of other fun stuff. It's commercial, so probably not up your alley if you're looking for something open source.
[1] http://www.axosoft.comIt may well be worth a look at Fixx [1]. I've done some work with the developers who created this, and they really know their stuff and create nice looking products. It's developing rapidly and seems to be very popular with their customers.
[1] http://hedgehoglab.com/products/fixxWe use Team Foundation Server on the current project. I think the setup of it is much too manual and it has its quirks, but it works at least for this project. Hopefully someone gives a detailed description of Mercury's TestDirector, it was the easiest to use for me but it's been a while.
Here's the Official Site [1]
[1] http://msdn.microsoft.com/en-us/vstudio/ff637362Here's another vote for Mantis [1].
@Camilo DR, source-control integration is available. I've got my mantis setup so that every time I do a SVN commit, the patch file is attached to the relevant issue along with the SVN comments being added as a note. I find this provides excellent history and lets you easily tie how an issue is resolved from the business side, to how it's resolved in the actual implementation. Here's the Tutorial [2] that I used to get this up and running. (It's definitely worth the effort.)
[1] http://www.mantisbt.orgI love Assembla [1]. We use it at work and I use it on a few side projects of my own. Integrated SVN, Tickets, Tasks, Milestones (Or you can just use Trac, which is also integrated).
The fewer things I have to host and maintain myself, the better. I like Trac a lot, but the installation and maintenance are a PITA.
[1] http://www.assembla.com/Mantis [1] again, with some custom modifications to cope internal requirements.
It's code is so "hackable" that I don't regret about work with it.
It will be better with the upcoming Plugins [2].
[1] http://www.mantisbt.org/We use MKS Integrity Manager [1] (+ Source Integrity as our scm) and I hate it. It's main features are complicated usage, slowness and a big love affair with "confirm" dialogs. If someone in your company wants to deploy that, run away quickly...
[1] http://www.mks.comWe used to work with Bugzilla, but thought we'd give Fogbugz [1] a try ... the difference is night and day. We're way more productive with all the features built right into FogBugz (scheduling, release prediction, rss feeds), and soon we'll even be opening up a community forum and wiki to share important information with our user community.
[1] http://www.fogbugz.comWe're using Telelogic Synergy - now IBM Rational synergy [1], and I wouldn't recommend it because it is not fast enough and not user friendly:
For instance, you can save a report, which is made of a query and a format. Then you have to erase and re-create your report you want to change either the query or the format.
For the speed, it could be due to the server we use (I have no detail), but the HTML page to display one CR weights more that 680 Kb, which make it long to display when you're away from the server.
EDIT: Also it does not differentiate between Defect and Change Request. A Defect reports an incident in the software while a Change Request is a request to fix the problem in a given version. Several Change Requests can be tied to the same Defect.
[1] http://www-01.ibm.com/software/awdtools/synergy/One client I work for uses Basecamp [1] for all client, project, time, and task tracking.
[1] http://basecamphq.com/My company uses JIRA [1] and Quality Center [2] along with a plugin to link both from Go2Group called JaM [3]. The reason for both is partly the cost of Quality Center, but also because QC doesn't have the right workflows we need for the developers.
JIRA integrates with Subversion and other versioning systems so you can look at a bug and easily see the commits that fixed the bug, etc. It's really great being able to extend the software as well.
[1] http://www.atlassian.com/software/jira/I use SourceForge Enterprise Edition [1] that is free under 10 dev. It's a VMWare with SVN, bug tracker, wiki and task manager. Very simple to use.
[1] http://www.vmware.com/appliances/directory/452My current client uses Google Docs [1] which is surprisingly good to allow non-technical people to collaborate on the bugs list as soon as you set up some basic ground rules (like marking comments with your initals and the date).
We use EPAM PMC suite [2] which is all-powerful RUP-oriented tool and occasionally Bugzilla [3] and Trac [4] on more agile projects.
[1] http://docs.google.comUsed to use RMTrack [1], now I use FogBugz. in my opinion RMTrack was superior because it supports customizing work flows, so you can get cases to escalate the way you want them to. We use loads of hacks with FogBugz to make it do what we want. We've esentially got a person who looks at it all day, making sure cases are with the right person to deal with them... we didn't need that with RMTrack.
[1] http://www.rmtrack.com/We used Team Foundation Server at work. I like it. At home I use Subversion with ankhsvn for VS.
I have a yellow legal pad that has all mine on it. The benefit of a team of one is no communication paths!
In our company we are using Polarion [1], an ALM solution that connects change management (task/bug tracking), wiki, version control (Subversion) and optionally also requirements management and build management.
Our company actually is Polarion Software, but we are using our own product not because we have to, but because we like to - making it the best for ourselves hopefully means making it the best for other users as well.
While addressing the highest ALM disciplines, Polarion also comes in a flavor called Track & Wiki [2], a rich-featured tracker and wiki integration at an affordable price. There was also a completely free tracker edition (without wiki) but that one is no longer maintained.
If somebody here ever tried Polarion and has something to say on why they prefer it to another tool or vice versa, I will be happy to know.
My reasons to use Polarion (from the user point of view) include:
My company uses Request Tracker [1] for support tickets. That is, client-reported bug tracking. It has some nice email integration features, and is highly configurable. Also open source, which was a requirement. (Of coruse, we also happen to use Bugzilla for internal bug tracking, so some RT tickets get double-logged, but that's not a terrible thing.)
[1] http://www.bestpractical.com/rtNo one has mentioned BugTracker.NET [1], personally I feel this to be quite good and free!
[1] http://ifdefined.com/bugtrackernet.htmlWe use Eventum [1] version 2.1.1. The key advantages of using it that we found are:
We've had an excellent experience with this software, after moving over from a highly expensive proprietary product. I highly recommend it.
[1] http://eventum.mysql.comAt my day job (essentially a 100% Microsoft shop) we use Windows SharePoint Services [1]. Not Microsoft Office SharePoint Server [2], which costs, but the free-with-Windows-Server version.
[1] http://office.microsoft.com/sharepointtechnologyLighthouse [1]. Integrates well with Beanstalk, which we use for our Subversion repository.
I am currently testing the desktop client Lighthouse Keeper [2] for the Mac. Looks nice, though I'm not sure it's worth the hassle. Different story with Cornerstone, the SVN client we use - worth every penny! I really recommend that to all SVN/Mac users.
-Gregor
[1] http://lighthouseapp.com/Fossil has a nice bug tracker built in see http://www.fossil-scm.org/
http://www.fossil-scm.org/index.html/doc/tip/www/bugtheory.wiki
Launchpad Bugs [1]
I'm gobsmacked no-one has mentioned it yet! I personally am an all-round Launchpad fan, and the bug/feature tracking system is certainly a great part of it.
[1] https://bugs.launchpad.net/Doesn't look like anyone has mentioned Open Atrium [1] yet. That is our tool of choice.
Beautiful UI and great for any size team, but not specifically aimed at developers. Built on Drupal so there are a lot of extensions coming out for it all the time and seems to be under very active development.
Have even had very non-technical clients who enjoyed working in it and using it as a project management system.
[1] http://openatrium.com/We currently use JIRA and Confluence. A nice mix with moderately good integration in our setup.
As a not very much a coder I've found JIRA relatively easy to administer, and the developers like it's 'zilla ness.
Philippe, your complaints of slow and non friendly with regard to Telelogic Synergy explains why IBM brought it!
We also use JIRA [1]. It's very easy to use, and also quite flexible, in that we started off using it just to track issues for software, and now use also it for hardware, testing and documentation. It helps that you pay for a site license, so are not limited to a particular number of users.
[1] http://www.atlassian.com/software/jira/I'm really amazed nobody has mentioned ' unfuddle [1]'.
It has SVN and git integration, time tracking, notebooks, milestones, tickets, messages, RSS, iCal, File Attachments, SSL and more.
The simplest plan is free, the rest of the plans are between $9 and $99.
It's not a high end tool for large and complex projects but it's a great tool for small or medium teams working on let's say web development projects.
I love the tool!
[1] http://www.unfuddle.comI currently use the Mantis bugtracker [1]. It's small and simple, but it has some great features like custom fields, very easy creation of new projects based on other projects (can copy settings, fields, user setup.)
I used Joel's FogBugz [2] at my last day job, it's awesome. Bugs always have owners in his system, so nothing falls through the cracks. One issue I had was that when a bug was resolved, it went back to the person that opened the bug- it would be nice to have the ability to send the bug to a specified person (eg. QA department) rather than defaulting to whoever opened it.
[1] http://www.mantisbt.org/Where I'm working, we use CA's Clarity for just about everything from financials to project management to bug tracking. Ugh.
The interface is ok, but it's slow and doesn't allow for easy batch entry/edit. I find it complete and total overkill, plus, because the whole company uses it, individual teams are unable to tweak it's configuration to suit their projects.
On the side, I'm floating between a couple products right now, and this post is giving me some insight into the tools out there, so thanks everyone for that.
Version control: Compuware TrackRecord [1]
Task/Bug Management: Mercury TestDirector [2]
I think we're using an older version of TrackRecord than the one listed on Compuware's site.. I'm really not impressed with TrackRecord. TestDirector is a pretty nice tool. It's easy to customize process work flows and define roles. It's pretty easy to script it for additional flexibility as well.
[1] http://www.compuware.com/products/qacenter/405_ENG_HTML.htmWe're using redmine [1] at the moment. Integrated bug tracking/task-tracking, wiki, forums, filestore, svn & other integration.
Very similar to Trac (which we trialled before), but more suited to a multi-project/multi-scm environment.
[1] http://www.redmine.org/Test Track Pro.
I would not describe it as my favorite, as its interface isn't going to win any awards in my book, but it seems to be able to support a pretty dynamic workflow if that is something important to you.
I use Redmine [1] for general project stuff and Flyspray [2] if I only need a bugtracker.
[1] http://www.redmine.org/I use a open source Domino web application called Bug Tracker.
It is available for free here:
http://www.openntf.org/Projects/pmt.nsf/ProjectLookup/BugTracker
It has some quirks, but it is free and works well....
I've used Eventum to good effects. It is made by the nice folks of MySQL. It has some nice user-support features, which are not available in other, pure development-oriented, tools.
http://eventum.mysql.org/wiki/index.php/Main_Page
In my current project we use bugzilla, but I don't like it that much. Mantis is very nice, specially because of the work flow.
We used to work with Mantis, then went to JIRA (Enterprise Edition). I've also worked with Bugzilla and redmine [1]
[1] http://www.redmine.org/We use VisionProject visionproject [1] we use it for customer support and internal development. (It has features to support scrum)
[1] http://www.visionproject.seI'm using Eventum [1] and find its not as complicated as bugzilla, also free and has a nice UI that doesn't scare the living daylights out of non-techies.
Why is Eventum not mentionend more often here or further up the top? Anything I've missed that makes not so popular ?
[1] http://dev.mysql.com/downloads/other/eventum/features.htmlWish I'd found Eventum when we were searching. :-/
We wound up writing our own; even simpler than Eventum. But it took plenty of hours.
http://www.archerfishonline.com
Would love some feedback.
We use JIRA for our bugtracking tool.
redmine here...
it's really simple and easy to set up and use...
BugNET (http://www.bugnetproject.com/). Works OK for small->medium sized projects. Been using it for 1-2 years.
Jira. Has some usability issues but coming from ClearQuest its fantastic :)
I havent used this personally, but it looks awesome: JetBrains Charisma...still in "beta" mode.
+1 for Gemini from CounterSoft. A great product at a relatively cheap price.
We use JIRA in conjunction with a desktop JIRA Client [1], which adds Outlook-like UI, desktop specific features like drag'n'drop, offline work etc.
[1] http://jiraclient.com/We use InTask ( www.InTaskPro.com [1]) since 2005 Very good tool - Fast, great modern UI, Multi user/Multi project, document versioning and lots more features. You can download free edition from: www.intaskpro.com [2]
Cons: It's not web based - some people think it's important (i'm not!)
[1] http://www.InTaskPro.comBugTracker.Net! It is great, source code provided, does many of the same things that FogBugz does.
SharePoint with the Bug Database template. [1] Simple, free(ish), extensible.
[1] http://www.microsoft.com/downloads/details.aspx?FamilyID=c72d23af-f556-47aa-a6f2-0027246a9928&displaylang=enRational ClearQuest [1]. Probably the worst source code control system ever designed. Practically unusable.
[1] http://www-01.ibm.com/software/awdtools/clearquest/I also use Google Docs for small projects I'm involved in. We've also found Google Notebook to be quite efficient. They may not have the scheduling features large groups need, but for sending snippets of code or quick design docs it works really well.
Gemini by CounterSoft. Not too complicated to use, it's not perfect but it's pretty decent stuff.
We use TFS for some reason!
hands down, bugzilla has been the best most configurable most accessible tool for bug tracking that I've had the pleasure to use. In a few cases, where it was lacking in some functionality, such as integration into visual source safe an attributing a particular bug to a particular build number, file and line number, I was able to add this functionality into our particular instance of bugzilla at a previous company I worked for.
We currently use Fogbugz. It is actually fairly nice and easy to use. Really good for small groups. We are looking using TFS atm but are not sure we want to with some of its quirks.
At one of my old jobs I used a custom hacked together coldfusion frankenstein that had been mutated over several years by a variety of programmers... after that almost anything is easier to use / better.
Previously I've used dotproject [1] (free and open source).
My current job uses Jira [2] (not free).
Both are good bug-task-project tracking tools for internal use. I haven't used either as customer facing tools so I'm not sure how they would work in that environment.
[1] http://www.dotproject.net/I have used TestTrackPro [1] by Seapine. Overall it worked quite well. I was able to set up custom work flows. The reporting does leave a lot to be desired however. Once I switched from using the native database to a SQL database I was able to write my own reports. There are much more powerful open source bug trackers out there and I would recommend one of those instead of TTP. Currently I am using JIRA and am quite happy with it.
[1] http://www.seapine.com/ttpro.htmlMy last job used Agile Zen (agilezen.com) for the Kanban team and Pivotal Tracker (pivotaltracker.com) for Scrum teams. Both are very good. Pivotal is free, but it's specifically designed for Scrum and isn't customizable if you aren't using Scrum or a similar Agile methodology.
I have recently started using this great little tool called phpEasyProject [1]
Its
TicGit-ng It's a distributed bug tracker that stores tickets in a 'ticgit' branch in your repository. Full disclosure, I'm the current active maintainer for TicGit-ng.
not really a bug tracker but we use jtrac if you need a workflow/ticketing system
you can also look at Calipso (based on jtrac)
Sadly we use Clarity which is very bad project management software for both projects and bugs. We used to use a homegrown application but senior management decided it didn't have enough bells and whistles, so they bought Clarity. Now it takes 3-4 times as long to do anything as far as managing tasks (or even filling in timesheets) and the messaging in it is so bad, that most of us handle any discussions through emails rather than keeping them in the project where they are hard to follow. Most of the windows won't filter by client, so I have to search through 8 or 9 pages of information to find the tasks I want to put on my timesheet.
I don't know who designed this software but they should be forced to used it 8 hours a day for a year.
Clarify (www.amdocs.com)
It's old and everyone here at work despises it. I don't think it was originally meant for bug tracking software, but for customer support cases. It's awful, hideous, and really really slow: I'd like some condolences please folks.... :)
Assembla's web based Bug Tracking system:
Allows you to track every stage and progress of an issue or bug Report on time invested, and estimated time remaining Attach files, or attach screenshots with the screen capture applet to annotate bug reports There's an activity stream where actions on the issue / ticket are posted
http://www.assembla.com/features/bug-tracking
I was inspired by FogBugz and Bugzilla and I made a custom bug tracking tool for my diploma thesis, which was used then in the first company I worked for.
