Bug Trackers
Moderator: General Moderators
-
Starcraftmazter
- Forum Commoner
- Posts: 45
- Joined: Mon Apr 24, 2006 11:36 pm
Bug Trackers
Hey.
I'm getting....getting to finishing a project, and I will be needing a bugtracker to track the bugs of the software.
Does anyone know any good php & mysql based bugtrackers? Something like what the guys at phpbb.com use would be great.
Thanks.
I'm getting....getting to finishing a project, and I will be needing a bugtracker to track the bugs of the software.
Does anyone know any good php & mysql based bugtrackers? Something like what the guys at phpbb.com use would be great.
Thanks.
I've found Mantis ( http://www.mantisbt.org/ ) quite useful some years back, not perfect, but best of the ones I reviewed.
A couple of years ago I searched for the best PHP bug tracker, and ended up with a Java solution being the best fit for our needs. We use Scarab, which is highly configurable out of the box and has worked well for our needs for several years.
-
Starcraftmazter
- Forum Commoner
- Posts: 45
- Joined: Mon Apr 24, 2006 11:36 pm
- Chris Corbyn
- Breakbeat Nuttzer
- Posts: 13098
- Joined: Wed Mar 24, 2004 7:57 am
- Location: Melbourne, Australia
- Ambush Commander
- DevNet Master
- Posts: 3698
- Joined: Mon Oct 25, 2004 9:29 pm
- Location: New Jersey, US
How we use Scarab may be different from most people straight bug tracking. We actually use the tool as our whole change management process. When we get a user request, we log an issue in Scarab. When I add a developer to the issue team, it emails them a notification, and any subsequent change is mailed to them. We have internal audits which require certain information to be entered and tracked, and we were easily able to add these fields to the issue types and track it. When we want to migrate code, we create a migration issue and the whole workflow of business owner approval, peer review of the code and production migration request is managed and tracked in the tool. Scarab deals well with attachments. We have even automated our release notes for major systems by adding a "release note" field to issues, scanning for issue related to a "master migration task" and aggregating the release note fields into a report. We condunct weeks staff meeting by pulling up Scarab and running queries for issues completed this week, outstanding migrations and prioritize open issue for each developer.
Again, Scarab is a java based tool, which is not the way I would normally lean, but it fit our processes so well out of the box that I have never needed to look under the hood to fix anything.
YMMV
Regards,
Jason
Again, Scarab is a java based tool, which is not the way I would normally lean, but it fit our processes so well out of the box that I have never needed to look under the hood to fix anything.
YMMV
Regards,
Jason
- feyd
- Neighborhood Spidermoddy
- Posts: 31559
- Joined: Mon Mar 29, 2004 3:24 pm
- Location: Bothell, Washington, USA
Mantis is okay, I feel. I dislike Bugzilla. It's never felt right when working with it.
Frankly, I have yet to find a decent one outside of Microsoft's RAID. Too bad it's in-house (or specially licensed out-of-house) and uses SQL Server along with some odd databasing with ODBC. It's a pain in the butt to set up, but once it's running, it works quite well. Anyway...
I'd like to build my own version of it. It's on my todo list.
Frankly, I have yet to find a decent one outside of Microsoft's RAID. Too bad it's in-house (or specially licensed out-of-house) and uses SQL Server along with some odd databasing with ODBC. It's a pain in the butt to set up, but once it's running, it works quite well. Anyway...
I'd like to build my own version of it. It's on my todo list.
- Ambush Commander
- DevNet Master
- Posts: 3698
- Joined: Mon Oct 25, 2004 9:29 pm
- Location: New Jersey, US
I checked out Mantis and there are a few notable problems:
1. No UTF-8 out-of-the-box!
(then again, neither does Bugzilla...)
2. At first blink, it looks like I'm going to edit core code to remove the huge "Mantis" logo on the default install. It doesn't even have a CSS hook for me to add display:none to. If I do that, it makes upgrading a huge pain, so if I do end up using Mantis, it'll be quite un-customized.
I was unable to find anything on RAID... what is it?
Also, I did some searching and came up with Flyspray and Eventum, any comments on them?
1. No UTF-8 out-of-the-box!
2. At first blink, it looks like I'm going to edit core code to remove the huge "Mantis" logo on the default install. It doesn't even have a CSS hook for me to add display:none to. If I do that, it makes upgrading a huge pain, so if I do end up using Mantis, it'll be quite un-customized.
I was unable to find anything on RAID... what is it?
Also, I did some searching and came up with Flyspray and Eventum, any comments on them?
Dug up my research thread from years ago:
http://www.phparch.com/discuss/index.ph ... 650df2bd5/
http://www.phparch.com/discuss/index.ph ... 650df2bd5/
- Ambush Commander
- DevNet Master
- Posts: 3698
- Joined: Mon Oct 25, 2004 9:29 pm
- Location: New Jersey, US
- feyd
- Neighborhood Spidermoddy
- Posts: 31559
- Joined: Mon Mar 29, 2004 3:24 pm
- Location: Bothell, Washington, USA
I've tried Flyspray.. but I can't recall why I dismissed it. I don't remember using Eventum, the name doesn't sound familiar.
As far as what RAID is, I'll try to explain it. As I said already, it's an internal software that they've produced and only allowed out to "special" partners. The last time I used it was 2001 I believe. Hopefully memory serves as I talk about how it worked and stuff. First thing you'd see after starting the application was the login screen. It worked off of roll-based access to various options, but for the most part everyone was equal. It was mostly so it could make creation a little bit easier and to optionally send emails to some various rolls.
Most often when we were working with it, changes to the bug would email the creator, whoever it was assigned to and the person doing the change. It supported attachments to each bug separately. When viewing a bug, it would display similarly to how bug.php.net displays; a history of changes, notes from various people involved and things. For example, if I changed a bug's status from "unresolved" to "not a bug" it would show something like "feyd changed status "unresolved" to "not a bug." So far this is somewhat standard sounding bug tracking software.
Where it shined was in how to look for bugs. To put it into web developer terms, it was Ajaxed to oblivion. The top pane was a resizable region with rows of combo boxes. Each row contained a box of some search keywords "not containing," "containing," etc; a field selection combo box; a contextually filled editable combo box based on the chosen field; and a combo box that would add another row with boolean linking "and," "or," and so forth.
All this really did was create an SQL query as far as I could tell. Each time you completed a row on the top pane it would populate the lower pane will matching bugs. Projects started with a fairly comprehensive set of fields, but could add their own custom fields if they wished too.
As far as what RAID is, I'll try to explain it. As I said already, it's an internal software that they've produced and only allowed out to "special" partners. The last time I used it was 2001 I believe. Hopefully memory serves as I talk about how it worked and stuff. First thing you'd see after starting the application was the login screen. It worked off of roll-based access to various options, but for the most part everyone was equal. It was mostly so it could make creation a little bit easier and to optionally send emails to some various rolls.
Most often when we were working with it, changes to the bug would email the creator, whoever it was assigned to and the person doing the change. It supported attachments to each bug separately. When viewing a bug, it would display similarly to how bug.php.net displays; a history of changes, notes from various people involved and things. For example, if I changed a bug's status from "unresolved" to "not a bug" it would show something like "feyd changed status "unresolved" to "not a bug." So far this is somewhat standard sounding bug tracking software.
Where it shined was in how to look for bugs. To put it into web developer terms, it was Ajaxed to oblivion. The top pane was a resizable region with rows of combo boxes. Each row contained a box of some search keywords "not containing," "containing," etc; a field selection combo box; a contextually filled editable combo box based on the chosen field; and a combo box that would add another row with boolean linking "and," "or," and so forth.
All this really did was create an SQL query as far as I could tell. Each time you completed a row on the top pane it would populate the lower pane will matching bugs. Projects started with a fairly comprehensive set of fields, but could add their own custom fields if they wished too.
It has been more than ten years since I did anything with Java, but once I was done emerging tomcat, it did not take much more time to get it up and rolling than any of the other PHP systems I tested. Could be problematic if you don't have administrative control over you system to add another web server though.Ambush Commander wrote:Scarab would be a pain to install though...
- Ambush Commander
- DevNet Master
- Posts: 3698
- Joined: Mon Oct 25, 2004 9:29 pm
- Location: New Jersey, US
Precisely. I only have non-root SSH access to a shared server, so installing it will be difficult.It has been more than ten years since I did anything with Java, but once I was done emerging tomcat, it did not take much more time to get it up and rolling than any of the other PHP systems I tested. Could be problematic if you don't have administrative control over you system to add another web server though.