Curious: Which Bug Tracking Software Does Your Team Use?
-
I'm quite curious about the bug tracking software that teams are using. Does your QA team use any bug tracking software at all? How do they report bugs to devs? Do they just send email or write the bug on a scrap of paper? If you do use anything, is it custom -- something written in-house? Or if it is a commercial or open-source package or other that is available, what is it called?
In the last year I've used Teamforge and Redmine. In the past I've also used irRational Clearquest X|, SharePoint (worked great as a simple bug list, especially since SP was familiar to our non-technical users), and (many years ago) Visual Intercept. Currently IT is soliciting interest in how many teams would be interested in replacing TeamForge with JIRA. Although they're currently calling it "voluntary" I expect that within a year they'll decide it'd be cheaper to shut down teamforge than to pay licensing fees for two trackers and force everyone else to switch as well.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
I'm quite curious about the bug tracking software that teams are using. Does your QA team use any bug tracking software at all? How do they report bugs to devs? Do they just send email or write the bug on a scrap of paper? If you do use anything, is it custom -- something written in-house? Or if it is a commercial or open-source package or other that is available, what is it called?
Our change request system (bugs, enhancements, new functionality) is built into the application (client/server, .NET, SQL Server). Users can request a change from within the application and it then goes through a management/development process. Works great for us.
-
I'm quite curious about the bug tracking software that teams are using. Does your QA team use any bug tracking software at all? How do they report bugs to devs? Do they just send email or write the bug on a scrap of paper? If you do use anything, is it custom -- something written in-house? Or if it is a commercial or open-source package or other that is available, what is it called?
We use mantis. It's not amazing, but it works. We know PHP and have modified the workflow (shocked it is not data driven to configure). But after customizing it and using it since it was Beta, it is kind of second nature. Our applications allow the end user to email in issues with/logs if they have crashes or problems. We had to put a simple script on the server to pull them into mantis. I agree. They all have drawbacks. We use a process where we RESOLVE things, and then the clients CLOSE them (okay, we close them during an interactive meeting with the Clients, as they confirm the resolved issue is published). We use it for 3 reasons: 1) Visibility/Planning 2) Communication/Process 3) EOM and EOY Summaries. Very cool to to show 70% of annual effort was on New Features!
-
I'm quite curious about the bug tracking software that teams are using. Does your QA team use any bug tracking software at all? How do they report bugs to devs? Do they just send email or write the bug on a scrap of paper? If you do use anything, is it custom -- something written in-house? Or if it is a commercial or open-source package or other that is available, what is it called?
We use Mantis company-wide. IMO it is adequate.
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
-
We use Mantis company-wide. IMO it is adequate.
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
Thanks. Mantis was one I stumbled upon and was taking a look at. Then I saw it was PHP. 'nuff said. :)
-
We use mantis. It's not amazing, but it works. We know PHP and have modified the workflow (shocked it is not data driven to configure). But after customizing it and using it since it was Beta, it is kind of second nature. Our applications allow the end user to email in issues with/logs if they have crashes or problems. We had to put a simple script on the server to pull them into mantis. I agree. They all have drawbacks. We use a process where we RESOLVE things, and then the clients CLOSE them (okay, we close them during an interactive meeting with the Clients, as they confirm the resolved issue is published). We use it for 3 reasons: 1) Visibility/Planning 2) Communication/Process 3) EOM and EOY Summaries. Very cool to to show 70% of annual effort was on New Features!
Thanks for the info. I had stumbled upon Mantis also and thought it looked relatively decent. Then I noticed that it is implemented in PHP. 'nuff said. :)
-
We use JIRA by Atlassian. It is Web-based, with great pricing that scales with the team size and budget needs. Features many useful plugins accessible via a Plugin Store[^]. Some are free, some are paid. Hope it helps!
Max
-
I'm quite curious about the bug tracking software that teams are using. Does your QA team use any bug tracking software at all? How do they report bugs to devs? Do they just send email or write the bug on a scrap of paper? If you do use anything, is it custom -- something written in-house? Or if it is a commercial or open-source package or other that is available, what is it called?
We use TFS for story management, defect tracking, source control and continuous integration. A one-stop shop that meets all our needs. IMHO, it works well. Very well. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Thanks for the feedback. I like the GitHub articlet too. It would be very cool to have something that integrated with Git &/or Hg so I could commit fixes, enter the bug number and then the same comment in the commit would go into the bug tracking software. Yes, I'm dreaming. :)
newton.saber wrote:
It would be very cool to have something that integrated with Git &/or Hg so I could commit fixes, enter the bug number and then the same comment in the commit would go into the bug tracking software.
I believe TFS will do that for you. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I'm quite curious about the bug tracking software that teams are using. Does your QA team use any bug tracking software at all? How do they report bugs to devs? Do they just send email or write the bug on a scrap of paper? If you do use anything, is it custom -- something written in-house? Or if it is a commercial or open-source package or other that is available, what is it called?
built my own a few years back to allow others to send me bug fixes, and feature requests. They can view the status on their own machines. The program does what it's good at; I've felt tempted to extend it further but can't justify the time (yet :-D )
-
We use TFS for story management, defect tracking, source control and continuous integration. A one-stop shop that meets all our needs. IMHO, it works well. Very well. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Very good to hear someone say they have an effective system in place. We'll just keep emailing our bugs around. :D Manager: "Why does this crash occur in production?" Dev: "Oh, I guess I missed the email with that bug." :wtf:
-
newton.saber wrote:
It would be very cool to have something that integrated with Git &/or Hg so I could commit fixes, enter the bug number and then the same comment in the commit would go into the bug tracking software.
I believe TFS will do that for you. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Ravi Bhavnani wrote:
believe TFS will do that for you
That's quite cool.
-
We use JIRA by Atlassian. It is Web-based, with great pricing that scales with the team size and budget needs. Features many useful plugins accessible via a Plugin Store[^]. Some are free, some are paid. Hope it helps!
Max
We use Jira, as well. It works great for what we need it for, and it integrates well with some of our other tools.
-
I'm quite curious about the bug tracking software that teams are using. Does your QA team use any bug tracking software at all? How do they report bugs to devs? Do they just send email or write the bug on a scrap of paper? If you do use anything, is it custom -- something written in-house? Or if it is a commercial or open-source package or other that is available, what is it called?
I order of the most I like to the ones I hate: 1- Trac: you can host it, you can add you plugins, it has wiki, there are hosted sites that can give you one repository, but can look old compared to today social media, but dude you don't want facebook if you are working. 2- Jira: could be better, have some features that I hate and consider useless. can be hosted or bought as a service. You can handle a lot of projects with this, have integration with all they products to give more services (Confluense...) 3- TFS: very good if you have a good admin working over it. The integration with VS is wonderful. 4- Spiceworks: a lower version of Jira, we ate it cause gave us a lot of problems.
-
I order of the most I like to the ones I hate: 1- Trac: you can host it, you can add you plugins, it has wiki, there are hosted sites that can give you one repository, but can look old compared to today social media, but dude you don't want facebook if you are working. 2- Jira: could be better, have some features that I hate and consider useless. can be hosted or bought as a service. You can handle a lot of projects with this, have integration with all they products to give more services (Confluense...) 3- TFS: very good if you have a good admin working over it. The integration with VS is wonderful. 4- Spiceworks: a lower version of Jira, we ate it cause gave us a lot of problems.
Great info. Thanks for the feed back. I think a lot of the difficulties with all of these systems is just the learning curve/ setup curve for getting everything set the way you want to use them.
-
In one way I hope you are joking. In another way -- since my QA people use nothing except outlook to report bugs -- I think you are on to a simple idea that really could work. I'm stuck in an endless looping paradox. :)
Here is an example of project on Excel Online[^]
-
I've used 1. TFS 2. BugZilla 3. OnTime 4. Axosoft 5. Excel 6. One Note 7. A homegrown app I wrote and some other one too
If it's not broken, fix it until it is
Did any of those win? :-D
-
I like the Bugzilla icons. HOnestly, it looks like one of the better ones, but looks possibly difficult to configure. But maybe they're all difficult to configure. :)
Not too difficult. There are some good tutorials to do this. Might take you a couple of hours (2 to 4) creating a bugzilla server on linux.
"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
-
I like the Bugzilla icons. HOnestly, it looks like one of the better ones, but looks possibly difficult to configure. But maybe they're all difficult to configure. :)
I've installed a bugzilla server and what the tutorials are lacking is things relating to the webserver part... I used apache2 and I had to first enable the website on the webserver (not in the tutorials) before it worked. If you can see apache2 start (index) page from your web browser, it tells you on there how to do it. Hope you find success (I almost gave up).
"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
-
I like the Bugzilla icons. HOnestly, it looks like one of the better ones, but looks possibly difficult to configure. But maybe they're all difficult to configure. :)
I've installed a bugzilla server and what the tutorials are lacking is things relating to the webserver part... I used apache2 and I had to first enable the website on the webserver (not in the tutorials) before it worked. If you can see apache2 start (index) page from your web browser, it tells you on there how to do it. Hope you find success (I almost gave up).
"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>