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?
-
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?
-
The other Max approves.
I'd rather be phishing!
-
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?
Long ago, we used something called Perfect Tracker. It had a web interface, with a custom search facility that was vulnerable to SQL injection attacks. Turned out to be its most useful feature...
-
I've tried to introduce bug tracking, really I have, when the only choice offered is TFS on a REALLY slow server it is a little difficult. Currently a user is most likely to stump up and bitch in the devs ear that his system is broken and he needs to fix it! Alternatively a printed page of excel list is left on his keyboard by some anonymous user. QA team hah hah hah hah hah hah hah hah hah hah hic!
Never underestimate the power of human stupidity RAH
I totally understand and guessed that at least 25% of the responders would say something like what you've said. I've experienced the same often. When I asked the QA team how they would track the bugs, they said, "uh, well, we can email them". Ugh!
-
Long ago, we used something called Perfect Tracker. It had a web interface, with a custom search facility that was vulnerable to SQL injection attacks. Turned out to be its most useful feature...
Staffan Bruun wrote:
vulnerable to SQL injection attacks
Bug tracking software with the bugs already in it. :)
-
Numerous people are moving to JIRA. I've used it and it feels quite bloated to me. I want something simple that reads my simple mind and makes my bug tracking simple. :) Good luck with the transition.
-
Bugzilla and its sufficient.
"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. :)
-
We are using a home made system - made 15 years ago and extended with web portal 10 years ago...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
BugZilla and notepad :-)
Add instant productivity to any windows application... http://www.funmouse.org
-
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?
Did you try Excel Online ?
-
Did you try Excel Online ?
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. :)
-
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?
TFS
-
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?
Used Redmine for a long time. Had all the features we needed and is open source. You can get a pre-configured turnkey linux copy here: http://www.turnkeylinux.org/redmine[^]
Eric
-
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. :)
