Actually, YaBB runs under PERL not PHP. Also, it uses flat files not a MySQL database.
 
However, the hosting provider does support PHP and MySQL so neither is a problem.
 
I'm also the one that originally brought the topic up. And I still do want to see it. I think that it has the potential to better communicate bugs to the developers and progress on squashing those bugs to the users.
 
I believe that GasGiant was going to work on getting a homebrew system of his up for use as a bug tracker for EvoERP. I, of course, am not the correct person to answer questions about that.

The bottom line is that it is a good idea, and ISTECH should reconsider it.
 
Kelloggs

That post was started 8 months ago.
 
Another 8 months on the table?
 
 
 

If it is a matter of money and resources, Our company can do it.
I can buy the domain/hosting and set up the software.
 
 
 
Kelloggs

Aaggghhhhrrrrmm.... Well... aren't we starting to see that certain people weren't so dumb and off base when they suggested to open the source code to paying customers.   Maybe, just maybe it would open the door toward some help with bug tracking. Now, if I could only remember who suggested that many times over the past 5 years....

Currently we have a list of bugs, that come from this forum and from customer complaints to Tech support. We try to duplicate them. and if we can then we try to fix them. There are some that we know are bugs but we can't duplicate and those are much much harder to fix. For example UMC reported a problem with APC and that it sometimes is missing the APINVT record and one side of the GL posting.  There have been a few others who report this happening to them too, but not many maybe 3 others.  So it is some configuration or circumstances that we can not duplicate here so it is much harder to catch this bug.. But we have sent out a special version to the users who have complained of this error, that tracks lines of code and  generates an audit file.. I did this about 2 weeks ago and I have had no feedback...
 
Most bugs that we can duplicate are emailed to programming and we fix them right away if we can, then they get sent to the person(s) who complained about them. The rest of the users get them with the next update, or if they have the same issue or request to be sent the fix we do so.
 
So our current bug list is really kept here on the forum, and through email reports to the programmers by tech support.

Quote from Kelloggs on 09/23/08 at 11:20:08:

 
Yes, I once again second this request. I would like a more transparent bug tracker at some point in the not so distant future.