Building the next osTicket without leaving its history behind
A major release can move the product forward while respecting the installations, contributors, and organizations that brought it here.
Progress with a memory
osTicket has been deployed, adapted, translated, and extended by organizations around the world. That history is not baggage. It is context for every architectural and product decision we make.
The next generation gives us room to rethink the help desk while keeping a clear upgrade path for the people already depending on it.
A new chapter should expand what is possible without erasing the trust already earned.
Open development creates accountability
Building in the open lets developers and long-time users see where the product is heading, challenge assumptions, and help us find the edges before a release reaches production.
The goal is not simply visibility. It is better work, informed by the people who understand the product in practice.