David Anderson

It’s been a few weeks since I’ve posted any real updates about the progression of FaultTrack. So what is the state of FaultTrack?

Performance Optimizations
Thanks to our pre-release testers, I was brought awareness of various performance issues in FaultTrack. I have spent a considerable amount of time doing performance analyzation runs on the software, and have made considerable improvements to performance in every area of the application. The performance in a deployed environment heavily relies on the speed of the database server serving your requests, but ultimately if you have a fast database server, FaultTrack will be holding its own just fine.

Bug Fixes
Before I branched the software to implement support for multiple databases, the software was committed to source control with zero known bugs. To date, there are still no known issues. This isn’t to say there won’t be any since I am still testing and polishing various parts of the system, but as of now there are no known issues.

Bug Reporting System
I like to get people involved, so I reached out to my friend Zack at Unified Technologies and had him develop the bug reporting feature in FaultTrack. After it was finished I ran it through QA, polished some things, and thus it has been included in FaultTrack.

Configuration System
A configuration system is being engineered to replace the one you see in the image below to make it a little more friendly and functional. I would mainly be adding support to configure multiple servers. I know I will use this feature, and in a real environment you may be using the same issue tracking software for multiple vendors, projects, workgroups, or even individually.

Support for Oracle’s MySQL Engine
Not everyone has access to a MSSQL Engine, so I felt it was important enough to set aside time from the normal business plan to implement. Side effects of this mean that you now must have .NET 4.0 Framework installed to use FaultTrack. This shouldn’t be an issue for most as it is included in Windows Update, so your system is likely to have it installed already, but for those who don’t FaultTrack will not run without it. Currently I have tested this with the MySQL 5.5 with great success. It uses the Microsoft ADO.NET Entity Framework which will allow me to provide more database support in the future.

That’s it for now. If you have feedback, or questions I would love to hear it. A release date has been set which I will not disclose as of yet, but it is very soon and you can look forward to all the FaultTrack’ing goodness. I will say that hosted solutions will be available for those who do not have access to any type of storage engine, but more details will be available when I release it.