Page 1 of 1

should I choose Mantis as a ticket management system

Posted: Jan 25, 2008 3:48 pm
by abird
I am looking for a ticket management system with the following requirements:
• Web Based
• Low price (<$1000 complete deployment), no per user seat requirement
• Needs to run on IIS
• Needs to support virtual directories, cannot require installation at root level
• Basic functions
o Ticket logging
o Customer views (customer needs to be able to log a ticket without accessing all internal information)
o Statistics / reporting
o Customized categorizations

It seems to me that mantis is good enough; would somebody advise about any possible issue with the above requirements.
Also, do I have to use MySQL or it can work with Oracle as well (the company uses Oracle as a database mostly).

Thanks
abird

Re: should I choose Mantis as a ticket management system

Posted: Jan 26, 2008 3:04 am
by vboctor
All the requirements are satisfied with Mantis with the exception of Oracle support which is experimental and is not guaranteed to work. The recommended databases for Mantis 1.1.1 is MySQL, MS SQL, or DB2. PostgreSQL is broken in 1.1.1, but will hopefully be fixed in 1.2.x releases.

Re: should I choose Mantis as a ticket management system

Posted: Feb 06, 2008 4:36 pm
by abird
is there any good help source to configure MySQL, IIS, and PHP5;

I am trying to run mantis but it doesn't work. I installed latest version of MySQL, PHP, IIS 6 and Mantis and when run imstart i got:

C:\InstantMantis>imstart
Starting Apache...
080206 13:33:21 [ERROR] Error message file 'C:\InstantMantis\server\mysql-4.1.16
-win32\share\english\errmsg.sys' had only 304 error messages,
but it should contain at least 652 error messages.
Check that the above file is the right version for this program!

C:\InstantMantis>mysqld: Unknown error 1146
080206 13:33:21 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgr
ade to create it.
(OS 10048)Only one usage of each socket address (protocol/network address/port)
is normally permitted. : make_sock: could not bind to address 0.0.0.0:8008
no listening sockets available, shutting down
Unable to open logs
080206 13:33:21 InnoDB: Started; log sequence number 0 43634
080206 13:33:21 [ERROR] Aborting

080206 13:33:21 InnoDB: Starting shutdown...
080206 13:33:24 InnoDB: Shutdown completed; log sequence number 0 43634
080206 13:33:24 [Note]

I got the same error for a regular Mantis and for InstantMantis.

Thanks in advance

Re: should I choose Mantis as a ticket management system

Posted: Feb 08, 2008 7:45 am
by dyawlak
It looks like you are running the Instant version, this should only be used for testing and not for live environments.

Re: should I choose Mantis as a ticket management system

Posted: Feb 08, 2008 2:50 pm
by PortVista
It works well as a ticket system that is geared toward software development, like if you wanted end users to report bugs. Although, the average non-computer literate person wouldn't know exactly what all the fields mean and may be offended if you choose "low priority" and "trivial" for his reports. Heck, I'm affraid to set that on my boss's issues.

Customers may be confused by some of the irrelevant fields that cannot seem to be hidden. Unless I missed a setting, you cannot make a "simple view" for customers which just show Subject, Description, and some resolutions. Fields like Status and Priority should be hidden...

Re: should I choose Mantis as a ticket management system

Posted: Feb 09, 2008 6:13 am
by dyawlak
PortVista wrote:It works well as a ticket system that is geared toward software development, like if you wanted end users to report bugs. Although, the average non-computer literate person wouldn't know exactly what all the fields mean and may be offended if you choose "low priority" and "trivial" for his reports. Heck, I'm affraid to set that on my boss's issues.

Customers may be confused by some of the irrelevant fields that cannot seem to be hidden. Unless I missed a setting, you cannot make a "simple view" for customers which just show Subject, Description, and some resolutions. Fields like Status and Priority should be hidden...

You need to know PHP and edit the files

Re: should I choose Mantis as a ticket management system

Posted: Feb 09, 2008 6:34 pm
by vboctor
You can check the status and any other enumerations. Check the following articles:

http://www.mantisbt.org/manual/manual.c ... values.php
http://www.mantisbt.org/manual/manual.c ... ations.php

Re: should I choose Mantis as a ticket management system

Posted: Feb 19, 2008 4:32 pm
by abird
thanks all for the information. I created a virtual 2003 server with IIS 6, Mysql5 and PHP5. Everything works together but I am having problems to run/install mantis. Is there a good installation guide?

thanks in advance

Re: should I choose Mantis as a ticket management system

Posted: Sep 07, 2009 3:15 am
by Eva Xu
I met the same error when I start apache.
The error is:
(OS 10048)Only one usage of each socket address (protocol/network address/port)
is normally permitted. : make_sock: could not bind to address 0.0.0.0:8089
no listening sockets available, shutting down
Unable to open logs

I installed mantis with Xampp.
Anyone can help me to fix the issue?
Thanks advance~