Bug recording and reporting packages.
-
I've been using BugTracker.NET for a year or so now, at two different companies. It isn't very slick, the colour scheme is awful, design is pretty messy. For for a team of 4-6 developers, a couple of testers, BA's and PM's it works OK. Especially considering the price (free). Takes about 10 minutes to setup if you have MS SQL and an available IIS server. It is easy to make a few modifications if you need them, although once you start that you get a desire to rewrite the entire thing :-) So personally I would recommend it, because it is easy to install, easy enough to use, does most things I can think you would want a bug tracking piece of software to do, and because it is free you don't need to justify the price to managers etc - which always seems to take a while. Good luck Andrew
Thanks mate. I've decided to take the plunge. I demoed it yesterday and it seems fine for my purpose. Thanks a lot.
SG Cause is effect concealed. Effect is cause revealed.
-
I realize I am opening up a can of worms here, but we need an easy to use bug recording package at my current company. One to record the bugs. Allow assigning of developers, updating status, generating reports, etc... Preferably with the ability to automatically assign, and respond by e-mail. Thanks for the input and abuse! Bill
We are using Mantis Bug Tracker for my company's projects. It is released under the GPL. You can pick it up at http://www.mantisbt.org/.
-
We use OnTime, and IMO, it's a steaming pile. They even goat-roped us into buying the add-ons that are supposed to improve performance and stability. It runs much slower now. The database design is worthy of The Daily WTF[^]. I believe they honestly use every database "design" mechanism I was ever taught not to use: Dynamic modification of key tables, stored procedures that generate and execute dynamic SQL, and more. It crashes regularly, and when it crashes, it sometimes randomly reconfigures some global interface settings. (I'm not kidding.) And it doesn't even matter on whose system it crashes, because in order to run it must have dbowner permissions on the database. Now, it could be that the only reason it works so terribly for us is that we try to organize our projects (dozens of project folders) or that we're a corporate shop with a cut-rate offshore team (thousands of defects). Apparently, they've spent all of their salary budget on marketing staff instead of competent developers, because their advertising and marketing is first-rate.
Grim (aka Toby) MCDBA, MCSD, MCP+SB SELECT * FROM users WHERE clue IS NOT NULL (0 row(s) affected)
-
I realize I am opening up a can of worms here, but we need an easy to use bug recording package at my current company. One to record the bugs. Allow assigning of developers, updating status, generating reports, etc... Preferably with the ability to automatically assign, and respond by e-mail. Thanks for the input and abuse! Bill
http://www.ifdefined.com/bugtrackernet.html[^] Bugtracker .Net
-
We are using Mantis Bug Tracker for my company's projects. It is released under the GPL. You can pick it up at http://www.mantisbt.org/.
What? No one is suggesting Bugzilla? It's worked flawlessly for us from day one. It's free, efficient, and just customizable enough without getting too complicated. It took a small amount of savvy to install it, but pretty much plugged right into our internal Apache server. If you can install Apache, you can install Bugzilla. As far as I can tell, it's the standard bug tracking package. There is a tremendous amount of support for it online. http://www.bugzilla.org/[^]
-
We're thinking about using this? Do you have any opinions on this product?
SG Cause is effect concealed. Effect is cause revealed.
We used bugtracker.net in our company too. IMHO it has a very intuitive UI, easy to setup and not overloaded with functionality. Good choice I think.
-
What? No one is suggesting Bugzilla? It's worked flawlessly for us from day one. It's free, efficient, and just customizable enough without getting too complicated. It took a small amount of savvy to install it, but pretty much plugged right into our internal Apache server. If you can install Apache, you can install Bugzilla. As far as I can tell, it's the standard bug tracking package. There is a tremendous amount of support for it online. http://www.bugzilla.org/[^]
We use BugZilla and I don't like it. The fact that they don't have multi-select listbox was disappointing. Maybe the new one has it, but we're on the last leg of the project.
There are II kinds of people in the world, those who understand binary and those who understand Roman numerals. Web - Blog - RSS - Math
-
I realize I am opening up a can of worms here, but we need an easy to use bug recording package at my current company. One to record the bugs. Allow assigning of developers, updating status, generating reports, etc... Preferably with the ability to automatically assign, and respond by e-mail. Thanks for the input and abuse! Bill
I've used FogBugz, and it worked for us. Personally, email filtering didn't work very well for us, but maybe it was never set up right. I've also used Bugzilla and that worked for us as well. And the price was right. :) Currently using TeamTrack. (No idea what the "business mashups" stuff is all about). Not enough experience yet to comment on it, but it seems more polished than either of the others. Good luck.
-
I realize I am opening up a can of worms here, but we need an easy to use bug recording package at my current company. One to record the bugs. Allow assigning of developers, updating status, generating reports, etc... Preferably with the ability to automatically assign, and respond by e-mail. Thanks for the input and abuse! Bill
Flyspray is another open source, web based, bug tracking system solution that we have been using for a couple months now and works well. http://www.flyspray.org[^] If has ability to automatically assign. E-mail notifications for a number of events. Updating Status And a host of other features (that we haven't gotten around to using yet). Good Luck!
-
I realize I am opening up a can of worms here, but we need an easy to use bug recording package at my current company. One to record the bugs. Allow assigning of developers, updating status, generating reports, etc... Preferably with the ability to automatically assign, and respond by e-mail. Thanks for the input and abuse! Bill
We use www.spiceworks.com While it is not a bug reporting and reporting package, we do use the trouble ticket part for tracking issues.
-
I realize I am opening up a can of worms here, but we need an easy to use bug recording package at my current company. One to record the bugs. Allow assigning of developers, updating status, generating reports, etc... Preferably with the ability to automatically assign, and respond by e-mail. Thanks for the input and abuse! Bill
I've used a few different ones. Currently we use Clearcase DIMS. It's a bit of a top-heavy app, but it works ok. We're transitioning to tracking defects via Quality Center. I can't say that I recommend doing that as so far it's been a mess to get setup and ported to. By far the easiest and simplest I've used is Mantis (http://www.mantisbt.org/[^]. It's simple to set up, easy to use, and if you have any php experience it's fairly easy to tweak.
-
We're thinking about using this? Do you have any opinions on this product?
SG Cause is effect concealed. Effect is cause revealed.
It is horrible. It was written by a guy as a way to learn asp.net. That's not just a put down, but a statement by the author. The author did not use code-behind and considers that a feature because you can just put a revised aspx file in the web site without recompiling. Stay away from bugtracker.net! My last employer forced me to implement this software for their issue tracking which was replacing an entirely paper based tracking system. They went with it purely because it was free. They weren't even willing to consider the $400 site license of another commercial product.
Michael Lang (versat1474) http://www.xquisoft.com/[^]
-
I realize I am opening up a can of worms here, but we need an easy to use bug recording package at my current company. One to record the bugs. Allow assigning of developers, updating status, generating reports, etc... Preferably with the ability to automatically assign, and respond by e-mail. Thanks for the input and abuse! Bill
-
We're thinking about using this? Do you have any opinions on this product?
SG Cause is effect concealed. Effect is cause revealed.
We've used Bugtracker daily for the past eight months. It's intuitive, has tons of features and does the great job for our team of five. We are opening it up to a larger group shortly. It does lack the auto-response, but being open-source you can add this feature. The code to do so in available but I haven't made this patch yet. It's highly configurable, especially if your tsql skills are average. There's also a excel export if the reporting is an important consideration. All in all I'd go with Trac, for the Project management/wiki features, but I'm in a .net shop so this works out well since the skillset to manage the system is inherent. Best wishes.
-
I realize I am opening up a can of worms here, but we need an easy to use bug recording package at my current company. One to record the bugs. Allow assigning of developers, updating status, generating reports, etc... Preferably with the ability to automatically assign, and respond by e-mail. Thanks for the input and abuse! Bill
Been working with Jira - and saw others using it too (and rather large companies). Cannot recall the entire feature list, but it did seem to have everything we needed. No stability issues.
-
I realize I am opening up a can of worms here, but we need an easy to use bug recording package at my current company. One to record the bugs. Allow assigning of developers, updating status, generating reports, etc... Preferably with the ability to automatically assign, and respond by e-mail. Thanks for the input and abuse! Bill
-
http://ifdefined.com/bugtrackernet.html[^]
Best wishes, Hans
[CodeProject Forum Guidelines] [How To Ask A Question] [My Articles]
We've been using BugTracker.NET for a couple of months now. It appears to have a fairly complete feature set. (I just use it, don't administer it.) David
-
I've been using BugTracker.NET for a year or so now, at two different companies. It isn't very slick, the colour scheme is awful, design is pretty messy. For for a team of 4-6 developers, a couple of testers, BA's and PM's it works OK. Especially considering the price (free). Takes about 10 minutes to setup if you have MS SQL and an available IIS server. It is easy to make a few modifications if you need them, although once you start that you get a desire to rewrite the entire thing :-) So personally I would recommend it, because it is easy to install, easy enough to use, does most things I can think you would want a bug tracking piece of software to do, and because it is free you don't need to justify the price to managers etc - which always seems to take a while. Good luck Andrew
I'm the author of BugTracker.NET. I've made some improvements in how BugTracker.NET looks "out-of-the-box", but if you still don't like the appearance, you have a lot of control via css and some other configuration files. Here is more info about customizing the appearance of BugTracker.NET: http://ifdefined.com/doc_bug_tracker_css.html
-
We've used Bugtracker daily for the past eight months. It's intuitive, has tons of features and does the great job for our team of five. We are opening it up to a larger group shortly. It does lack the auto-response, but being open-source you can add this feature. The code to do so in available but I haven't made this patch yet. It's highly configurable, especially if your tsql skills are average. There's also a excel export if the reporting is an important consideration. All in all I'd go with Trac, for the Project management/wiki features, but I'm in a .net shop so this works out well since the skillset to manage the system is inherent. Best wishes.
-
It is horrible. It was written by a guy as a way to learn asp.net. That's not just a put down, but a statement by the author. The author did not use code-behind and considers that a feature because you can just put a revised aspx file in the web site without recompiling. Stay away from bugtracker.net! My last employer forced me to implement this software for their issue tracking which was replacing an entirely paper based tracking system. They went with it purely because it was free. They weren't even willing to consider the $400 site license of another commercial product.
Michael Lang (versat1474) http://www.xquisoft.com/[^]
I'm the author of BugTracker.NET. This might be the statement that Mike Lang is referring to, from the BugTracker.NET documentation at http://ifdefined.com/doc_bug_tracker_programmers.html#code I started BugTracker.NET in 2002 as a learning project, to teach myself .NET and C#, to get those technologies on my resume. At the time I didn't own Visual Studio, so I went about learning .NET the same way I had learned Java in its early days: I downloaded the SDK, edited files using a text editor, and compiled using the command line. If you work with the SDK and the documentation of for the .NET libraries, you won't even come across the term "code-behind". Code-behind is a Visual Studio concept, not a .NET concept. I didn't know about code-behind when I created BugTracker.NET and so BugTracker.NET does not use that technique. It's not a philosophy. It's just how I happened to start the coding. Mike Lang, I'd be interested in your critique of BugTracker.NET's functionality, as opposed to the coding style.