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?
-
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'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
-
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 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.
-
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'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'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
-
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
The other Max approves.
I'd rather be phishing!
-
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 are going to switch to JIRA in a few months... I'm glad to hear it is good...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
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'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?
FogBugz baby yeah! :thumbsup:
-
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?
Just to chime in here, I'm quite happy nowadays using GitHub's issue tracker. And it was painless[^] to integrate into the client's website, so they can keep tabs on issues. :) That said, I've worked with several others, and as others have posted, they all pretty much suck. One day I will write a decent bug tracker, one that is configurable to the project needs, isn't dog slow, doesn't clutter your screen with a ton of "I don't give a shit about that field", is interactive rather than just statically showing issues, easily quantizable (think "sprints" but don't think "sprints") And by interactive, I mean being able to say "here's some issues I'll be working on" and it could ask how progress is going, what issues / dependencies have been encountered, etc. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
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.
-
Nemanja Trifunovic wrote:
It sucks,
Thanks for feedback on Bugzilla. Also, that is the same thing I've found. They all mostly suck.
-
I've heard of Fogbugz because I've heard of Joel On Software. Thanks for the feedback.
-
Great link. Didn't know that existed. Thanks very much. Sorry for the rerun. :)
-
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
Thanks for the feedback. I see your comment us upvoted by someone else too, so maybe they are chiming in that JIRA is not too bad?
-
Just to chime in here, I'm quite happy nowadays using GitHub's issue tracker. And it was painless[^] to integrate into the client's website, so they can keep tabs on issues. :) That said, I've worked with several others, and as others have posted, they all pretty much suck. One day I will write a decent bug tracker, one that is configurable to the project needs, isn't dog slow, doesn't clutter your screen with a ton of "I don't give a shit about that field", is interactive rather than just statically showing issues, easily quantizable (think "sprints" but don't think "sprints") And by interactive, I mean being able to say "here's some issues I'll be working on" and it could ask how progress is going, what issues / dependencies have been encountered, etc. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
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. :)
-
Great link. Didn't know that existed. Thanks very much. Sorry for the rerun. :)
:thumbsup: Have found several circular references here. Answers to many questions are found here itself, so CP is kind of a self-sufficient universe. No need of Google, Bing, etc.
-
That's quite a mature system. Is it non-intrusive ie - not annoying to use? Just curious. Thanks for the feedback.
As it was originally tailored for our support team and matured with that team (with additions and fixes per request) it is very easy to use - for the team at least. I can't promise that everyone will find it easy-to-use, after all it has a rather old UI... But for us it is the best...Now that there is a plan to move to JIRA we all scared a bit...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
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?
Back when I was a rookie, we used this tracking system[^]. I would not exactly call it software. It was more like a pile of analog electronics with a analog computer.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns.
