September 5th, 2007
As we expanded our portfolio, number of testers and bug reports in our company increased greatly. Sometimes they would send me bug reports on email, sometimes over IM or in person on coffee break and so on. We were never too formal and I always enjoyed relaxed atmosphere but enough is enough. If somebody asked us who’s taking care of some issue he would get the answer only if directly involved programmer was around, otherwise nobody even knew about the issue – it was between user or tester and one programmer.
And it is of great importance for project to be successful that everybody knows what others are doing and what are their priorities. You can’t say it’s not my problem, you must say its Mario’s or John’s problem. Also, looking through your list of issues it’s much easier to arrange your priorities and be more effective.
So I went hunting for a bug tracker tool. It looks like there is tool for every pocket and server. PHP – Apache – MySql combination is prevailing in free open source field. Commercial and freeware tools all look the same in general and cover all the same functionality in different ways. In the end, somehow I discovered this little gem called BugTracker.NET. If I had time to write such a project I would probably wrote it this way. It’s free and open source, configurable to the smallest details without recompiling and works on IIS and SQL database, it’s written in ASP.NET and it’s easy to read. I fell in love immediately.
In one evening I’ve set up BugTracker.NET for all our projects and for all our testers. I renamed it to Issue tracker and in a week, everybody had BugTracker.NET as main reference for project status. Generating project reports and estimating programmer’s workload was never easier. Bugs, task and features all found a place in this tool and using bugtracker’s email notifications has done more for my mailbox then Thunderbird when I migrated from Outlook express: it was finally useful.
As author put it: Bugtraker.NET is poor-man’s FogBUGZ. I say it’s not about the money, it’s about simplicity.
5 Responses to “Bugtracker.NET – rediscover your bugs”
October 27th, 2008 at 17:28
Great you found the right bug tracker for you. If you’d like to use test management that integrates with BugTracker.NET, please check out our baby Testuff (http://www.testuff.com). It allows you to export bugs to BugTracker.NET as you do your manual testing. We’ve just added the integration, so we’d love to get some feedback about it.
November 7th, 2008 at 20:49
I was interested in knowing from a user how Bugtracker.NET is with web
services, especially importing bugs found by users.
February 23rd, 2009 at 17:37
I need help, when i attach a file to case return an invalid Id
March 10th, 2009 at 17:29
@Manena
I had the same Problem, I fixed it by replacing add_attachemen.aspx with the one from the latest bt.net version. When you do so you will get error messages, I just replaced/added the lines that gave me error messages with the ones from the old file and it worked
https://sourceforge.net/forum/message.php?msg_id=6725547
April 9th, 2009 at 13:37
Just like Barry Kottler, I was interested how Bugtracker.NET works with web
services.