Simpleticket Mission
I thought it might be helpful to restate what ‘our’ mission was when creating a SimpleTicket.
Architel wanted to create a ticket system that was SIMPLE and easy to use. We wanted to take advantage of cool presentation features like Ajax and great UI (we still need some help there) for the users. We did not want to create a ticketing system that could do everything, just a few things well. Less is more was our moto. There are several other open source ticketing systems, but none of them were right for our company. Why? They were written by people who wanted to use them instead of for the people who needed them Just spend some time with them. They have way too many options and features and those option and features make them terribly difficult to use. Most traditional (low tech) businesses don’t use ticketing systems because they are 1) too expensive and/or 2) too complicated to understand. We want SimpleTicket to be written for any business with between 1 and 20 IT professionals. We don’t want SimpleTicket to be written to support an ISP or an IT support company.
To summarize, SimpleTicket should be:
- Simple
- Easy to Use
- Easy on the Eyes
- Limited Feature Set
- Perfect for an IT department (1-20 IT professionals)
That said, we know that there is room for other versions of SimpleTicket. More complicated and feature-rich versions. Perhaps once the code is clean and the release is stable we can create a permanent branch called SimpleTicket Pro. In any event, our roadmap (after the next two releases) includes an API that will allow anyone to create any sort of ‘plug-in’ they desire for SimpleTicket. This way, you can make SimpleTicket as complicated as you want to. We will keep thinking about having a ‘Pro’ branch/version, but be certain that our plug-in strategy will allow for almost any use desired by the community. But we never want to lose sight of our target client – keep SimpleTicket simple – please!
