[iOliverC]

Hey guys,

Does anyone know of a decent bug tracker? I want something simple (meaning no BugZilla), but also allows for multiple-projects.

I've heard Mantis is good, but can't figure out how to install it.

Thanks,
Oliver

[Diggory Laycock]

Originally posted by iOliverC:

I've heard Mantis is good, but can't figure out how to install it.

The install documentation doesn't seem too unusual - have you got MySQL installed?

Which parts are you having problems with?

[Angus_D]

Mantis is pretty straightforward (as Diggory said, what exactly is it that you don't get?). If you want something a bit heavier weight, look at JIRA (not cheap). RT also looks good, but is less traightforward to set up.

[iOliverC]

Well, firstly I only have limited experience with MySQL, but I have set up a few stuff with it.

At first, I did not realise there was no config_inc.php file, which is needed to set it up, so I copied the config_inc.php.sample into a config_inc.php file. Configured all of that file and uploaded, I got a error saying Mantis could not access my database which i had set up, I tried multiple settings and none worked. Although it probably isn't Mantis that's the problem, more likely my server (which I hate, DreamHost).

I guess I'll give it more of a go later today, its just annoying that there is no manual or anything with it (but I guess thats what you get with a 0.19 release).

Thanks,
Oliver

[Diggory Laycock]

Trouble with this part?

Code:
	# --- database variables ---------

	# set these values to match your setup
	$g_hostname      = "localhost";
	$g_db_username   = "root";
	$g_db_password   = "";
	$g_database_name = "bugtracker";

Can you connect to the DB using the settings you used and http://cocoamysql.sourceforge.net/ ?

[Angus_D]

Originally posted by Diggory Laycock:
Can you connect to the DB using the settings you used and http://cocoamysql.sourceforge.net/ ?

If he's using a hosting company then probably not, since most sane people block MySQL TCP connections other than from localhost in those sorts of environments.

[iOliverC]

Originally posted by Diggory Laycock:
Trouble with this part?

Code:
	# --- database variables ---------

	# set these values to match your setup
	$g_hostname      = "localhost";
	$g_db_username   = "root";
	$g_db_password   = "";
	$g_database_name = "bugtracker";

Can you connect to the DB using the settings you used and http://cocoamysql.sourceforge.net/ ?

Yep, thats the bit. I'l give connecting with CocoaMySQL a go.

Thanks,
Oliver

[hayesk]

I'm building one in FileMaker Pro, but it won't be ready for several months.

[Diggory Laycock]

This link:

http://www.wombatnation.com/misc/ins...DreamHost.html

may help you with the DB stuff and your hosting people.

[Angus_D]

Originally posted by hayesk:
I'm building one in FileMaker Pro, but it won't be ready for several months.

*shudder*

[hayesk]

Originally posted by Angus_D:
*shudder*

Care to explain?

I would think one would use a database program to make a database. It's certainly a lot quicker than coding it in Cocoa or PHP. Unless you prefer hand-editing tables in MySQL?

[Angus_D]

Originally posted by hayesk:
I would think one would use a database program to make a database.

FileMaker is only just starting to resemble a real database. It still has scaling issues, AFAIK, and certainly isn't cheap to deploy.

I would think one would use an existing solution based on a REAL database rather than rolling one's own in some crazy proprietary solution which is widely regarded as a "low-end" solution.

I would think that having a web-based interface would be an advantage. FileMaker hosting is not cheap, whereas you could shove Mantis on pretty much any semi-decent web host out there.

It's certainly a lot quicker than coding it in Cocoa or PHP. Unless you prefer hand-editing tables in MySQL?

Yes, I'd actually rather do that than use FileMaker. Or Access.

[hayesk]

Originally posted by Angus_D:
FileMaker is only just starting to resemble a real database. It still has scaling issues, AFAIK, and certainly isn't cheap to deploy.

Oh give me a break. You sound like a WinTroll. That so-called "fake" database has earned me thousands of dollars and many happy customers. They're happy because they saved tens of thousands of dollars by not having to hire MySQL/PHP consultants to manage their databases. They can use and maintain FileMaker by themselves.

I would think one would use an existing solution based on a REAL database rather than rolling one's own in some crazy proprietary solution which is widely regarded as a "low-end" solution.

I would love to hear your definition of a "real" database. See if you can do it without mentioning a product name. MySQL is fine, but it's only a back end. Users generally want an interface to actually use the data. PHP, Cocoa, Java, etc. clients all take significantly more development time. Time is money. The original poster already had trouble with MySQL. I can guarantee he wouldn't have that trouble with a FileMaker-built solution.

I would think that having a web-based interface would be an advantage. FileMaker hosting is not cheap, whereas you could shove Mantis on pretty much any semi-decent web host out there.

FileMaker can do web hosting, and not everyone needs it hosted by a third-party server. The original poster just wanted a bug tracking database with no more information. It could be standalone, could be small workgroup in his office, it could be for the public to submit bugs. We really aren't in a position to disqualify any product.

Yes, I'd actually rather do that than use FileMaker. Or Access.

Wow, such prejudice. Other people just want to manage their data quickly and easily so they have time to do other things.

[Angus_D]

Originally posted by hayesk:
Oh give me a break. You sound like a WinTroll. That so-called "fake" database has earned me thousands of dollars and many happy customers. They're happy because they saved tens of thousands of dollars by not having to hire MySQL/PHP consultants to manage their databases. They can use and maintain FileMaker by themselves.

They shouldn't need to maintain a fecking bug tracker themselves. The application should shield them from the implementation details, like the fact the backing store is a database.

I would love to hear your definition of a "real" database.

Having multiple tables and proper relations is a start.

Users generally want an interface to actually use the data.

Yes, and for situations where a custom solution is really necessary and the entry bar needs to be low, FileMaker blows the competition away. This is not one of those times.

[QUOTEFileMaker can do web hosting, and not everyone needs it hosted by a third-party server. The original poster just wanted a bug tracking database with no more information. It could be standalone, could be small workgroup in his office, it could be for the public to submit bugs. We really aren't in a position to disqualify any product.[/QUOTE]No, but tbh installing Mantis is really quite straightforward (I did it on a hosting provider's server in a few minutes, iirc), then you can access it from any browser.

Wow, such prejudice. Other people just want to manage their data quickly and easily so they have time to do other things.

No, I'm not prejudiced. I'm just an advocate of using the right tool for the right job. In this particular case, FileMaker is not the right tool. An existing issue management solution is. And I personally wouldn't like to deal with FileMaker because I have had bad experiences with it in the past, due to its lack of real relations and basic things like that. Also, it's only customizable up until a point. Like I said, good for low-end stuff but you're going to hit those walls quite soon if you go beyond that. And when you do, you'll realise that they're very tall walls.

[hayesk]

Originally posted by Angus_D:
They shouldn't need to maintain a fecking bug tracker themselves. The application should shield them from the implementation details, like the fact the backing store is a database.

My customers wanted to add their own features and customize the web pages. My customers want to back up their data from their database server. They found FileMaker easier and cheaper.

Having multiple tables and proper relations is a start.

Filemaker does support multiple tables (yes, within the same file, if you like) and proper relations. It sounds like you haven't looked at FileMaker in a while.

Yes, and for situations where a custom solution is really necessary and the entry bar needs to be low, FileMaker blows the competition away. This is not one of those times.

I would think a bug tracking database would be one of those times. The user is free to add fields, make new reports, etc. I can't think of an easier product to do this in.

No, but tbh installing Mantis is really quite straightforward (I did it on a hosting provider's server in a few minutes, iirc), then you can access it from any browser.

Hmmm... same with FM. But regardless, the poster had trouble.

And I personally wouldn't like to deal with FileMaker because I have had bad experiences with it in the past, due to its lack of real relations and basic things like that.

In other words you are judging the FileMaker of today with what you deemed to be a shortcoming in the past, and have no idea what it is capable of today. FileMaker now has multiple tables, "true" relations (you can even do comparison relations like key > foreign_key), and a great security model. It's like saying Macs suck because they only have 9" black and white screens.

Also, it's only customizable up until a point. Like I said, good for low-end stuff but you're going to hit those walls quite soon if you go beyond that. And when you do, you'll realise that they're very tall walls.

Challenge me with one of these "walls". There are a lot fewer than what you think. I'm not making the thing out to be Oracle coupled with a team of developers, but it's a heck of lot more advanced than you seem to think it is.

[tyrrell]

We used FileMaker for YEARS to track bugs in QuickMail, QuicKeys and anything else ever offered by CE. It may not be a relational powerhouse, but it certainly will suffice for tracking bugs.

In the way we used it, I can't imagine why anyone would want relations. I could see it if you were tracking support calls and customers and needed to tie it all together, but even then, FileMaker would suffice.

I probably have a clone of a bugbase in FileMaker that I can provide (clone - no data of course) to whomever wants it. I'm sure I'd have to do some searching to find it though. And it's setup to work for the process we used at CE, but may not fit your process at all.


Best wishes,
Chris (who is no longer with CE)

[Bwa]

MySQL is not exactly a "real" database. :-)