PHP JavaScript CSS Tcl Shell HTML Other
#2 Compare This branch is 3 commits behind osTicket:develop.
Failed to load latest commit information.
api Make API requests stateless Jul 12, 2013
assets Fix spelling error in documentation Aug 1, 2014
css Fix parsing issue in strtotime() Oct 31, 2013
images Add overlay & loading spinner to client interface - shown on form sub… Feb 15, 2013
include i18n: Ensure UTF-8 is used as the request encoding Apr 2, 2015
js Only fetch client and scp config on pages with file upload Jul 24, 2013
kb Properly define ROOT_PATH Aug 2, 2013
pages Properly define ROOT_PATH Aug 2, 2013
scp login: Require CSRF token to login Mar 10, 2015
setup Fix typo in suggested permissions for config file Aug 1, 2014
.gitignore Add package script and scripts/ folder for scripts Jan 2, 2013
LICENSE.txt 1.7 Developer Pre-Release Mar 19, 2012
README.md Add credit to phpseclib Sep 3, 2013
UPGRADING.txt Update release notes for v1.7.3 Oct 31, 2013
WHATSNEW.md Add release notes for v1.7.14 Apr 2, 2015
ajax.php Use util method - get_path_info() Mar 7, 2013
attachment.php Update copyright (c) to 2013! Feb 19, 2013
captcha.php Update copyright (c) to 2013! Feb 19, 2013
client.inc.php Fixes ROOT_PATH detection on Windows Sep 18, 2013
index.php Use DB based pages for landing, offline and thank-you pages. Jul 3, 2013
l.php Update copyright (c) to 2013! Feb 19, 2013
login.php login: Require CSRF token to login Mar 10, 2015
logo.php Allow custom logo integration on client site Jul 17, 2013
logout.php Update copyright (c) to 2013! Feb 19, 2013
main.inc.php Merge pull request #861 from greezybacon/issue/858 Dec 2, 2013
offline.php Fix logo display in offline mode Aug 9, 2013
open.php Make captcha text case-insensitive Oct 28, 2013
secure.inc.php Allow custom logo integration on client site Jul 17, 2013
tickets.php Move $_FILES reformatting & validation to class.file.php Mar 4, 2013
view.php Support auto-login if auth token is available. Oct 3, 2012
web.config Fixup web.config for newly patched IIS May 15, 2014



osTicket is a widely-used open source support ticket system. It seamlessly integrates inquiries created via email, phone and web-based forms into a simple easy-to-use multi-user web interface. Manage, organize and archive all your support requests and responses in one place while providing your customers with accountability and responsiveness they deserve.

How osTicket works for you

  1. Users create tickets via your website, email, or phone
  2. Incoming tickets are saved and assigned to agents
  3. Agents help your users resolve their issues

osTicket is an attractive alternative to higher-cost and complex customer support systems; simple, lightweight, reliable, open source, web-based and easy to setup and use. The best part is, it's completely free.


osTicket now supports bleeding-edge installations. The easiest way to install the software and track updates is to clone the public repository. Create a folder on you web server (using whatever method makes sense for you) and cd into it. Then clone the repository (the folder must be empty!):

git clone https://github.com/osTicket/osTicket-1.7 .

osTicket uses the git flow development model, so you’ll need to switch to the develop branch in order to see the bleeding-edge feature additions.

git checkout develop

Follow the usual install instructions (beginning from Manual Installation above), except, don't delete the setup/ folder. For this reason, such an installation is not recommended for a public-facing support system.


osTicket supports upgrading from 1.6-rc1 and later versions. As with any upgrade, strongly consider a backup of your attachment files, database, and osTicket codebase before embarking on an upgrade.

To trigger the update process, fetch the osTicket-1.7 tarball from either the osTicket github page or from the osTicket website. Extract the tarball into the folder of your osTicket codebase. This can also be accomplished with the zip file, and a FTP client can of course be used to upload the new source code to your server.

Any way you choose your adventure, when you have your codebase upgraded to osTicket-1.7, visit the /scp page of you ticketing system. The upgrader will be presented and will walk you through the rest of the process. (The couple clicks needed to go through the process are pretty boring to describe).

WARNING: If you are upgrading from osTicket 1.6, please ensure that all your files in your upload folder are both readable and writable to your http server software. Unreadable files will not be migrated to the database during the upgrade and will be effectively lost.

View the UPGRADING.txt file for other todo items to complete your upgrade.


Visit the wiki or the forum. And if you'd like professional help managing your osTicket installation, commercial support is available.


Create your own fork of the project and use git-flow to create a new feature. Once the feature is published in your fork, send a pull request to begin the conversation of integrating your new feature into osTicket.


osTicket is released under the GPL2 license. See the included LICENSE.txt file for the gory details of the General Public License.

osTicket is supported by several magical open source projects including: