The osTicket open source ticketing system official project repository, for versions 1.8 and later
PHP JavaScript CSS Shell Perl HTML
Latest commit 4cc6a35 Mar 23, 2017 @aydreeihn aydreeihn committed on GitHub Merge pull request #3714 from samdsmx/develop
Update README.md
Permalink
Failed to load latest commit information.
api api: Use sessions for API — required for SSO Jan 6, 2015
apps lint: Fix several issues from regression tests Apr 2, 2014
assets End user avatar fix for #2557 #2580 Oct 1, 2015
css Merge pull request #3356 from JediKev/bugfix-estonianFlag Oct 24, 2016
images avatar: Add initial artwork for built-in avatars Aug 4, 2015
include Merge pull request #3714 from samdsmx/develop Mar 23, 2017
js files: Drop parallel uploads Jun 11, 2016
kb files: Provide unified download script Dec 31, 2014
pages oops: Fix crash rendering attachments for FAQ articles May 13, 2015
scp banlist Dec 16, 2016
setup Merge remote-tracking branch 'osticket-develop/develop' into patch-17 Dec 15, 2016
.gitignore no message Feb 16, 2015
ISSUE_TEMPLATE.md issue template Dec 12, 2016
LICENSE.txt 1.7 Developer Pre-Release Mar 19, 2012
README.md Update README.md Jun 8, 2016
UPGRADING.txt Update release notes for v1.7.3 Oct 31, 2013
WHATSNEW.md Add release notes for v1.10 Nov 1, 2016
account.php Internal error occurred #3 (with a lot more internal error occurred r… Jun 3, 2016
ajax.php draft: Put inline image draft race to rest Dec 8, 2014
avatar.php staff profile avatar does not change until [Save Changes] Aug 4, 2015
bootstrap.php Add Trusted Proxies and LAN Options Nov 1, 2016
captcha.php Update copyright (c) to 2013! Feb 19, 2013
client.inc.php Add concept of permissions for users, orgs, search Mar 5, 2015
file.php Lint fixes Oct 24, 2016
index.php Translation issues on homepage and kb page Jun 6, 2016
login.php Merge remote-tracking branch 'osticket-develop/develop' into patch-17 Dec 15, 2016
logo.php Allow custom logo integration on client site Jul 17, 2013
logout.php session: Move cookie routines to session class Feb 6, 2015
main.inc.php Update/Unify all the `Get tech(nical) help/support`phrases to `Get te… Dec 16, 2016
manage.php cli: Fix crash deploying with --setup Sep 18, 2015
offline.php Adopt translation work from Thane de Loth Jun 25, 2014
open.php Update all `Try again!` phrases to `Please try again` :) Jun 14, 2016
profile.php Profile update for clients Mar 20, 2014
pwreset.php Internal error occurred #3 (with a lot more internal error occurred r… Jun 3, 2016
secure.inc.php Redirect to originally-requested page on login Mar 25, 2014
tickets.php Internal error occurred #3 (with a lot more internal error occurred r… Jun 3, 2016
view.php Users can visit more than one ticket via link Jun 6, 2014
web.config Merge remote branch 'upstream/develop' into develop-next May 15, 2014

README.md

osTicket

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.

Requirements

  • HTTP server running Microsoft® IIS or Apache
  • PHP version 5.4 or greater, 5.6 is recommended
  • mysqli extension for PHP
  • MySQL database version 5.0 or greater

Recommendations

  • gd, gettext, imap, json, mbstring, and xml extensions for PHP
  • APC module enabled and configured for PHP

Deployment

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

And deploy the code into somewhere in your server's www root folder, for instance

cd osTicket
php manage.php deploy --setup /var/www/htdocs/osticket/

Then you can configure your server if necessary to serve that folder, and visit the page and install osTicket as usual. Go ahead and even delete setup/ folder out of the deployment location when you’re finished. Then, later, you can fetch updates and deploy them (from the folder where you cloned the git repo into)

git pull
php manage.php deploy -v /var/www/htdocs/osticket/

Upgrading

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 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).

Upgrading from v1.6

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.

After upgrading, we recommend migrating your attachments to the database or to the new filesystem plugin. Use the file command-line applet to perform the migration.

php manage.php file migrate --backend=6 --to=D

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

Help

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

Contributing

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.

Localization

Crowdin

The interface for osTicket is now completely translatable. Language packs are available on the download page. If you do not see your language there, join the Crowdin project and request to have your language added. Languages which reach 100% translated are are significantly reviewed will be made available on the osTicket download page.

The software can also be translated in place in our [JIPT site] (http://jipt.i18n.osticket.com). Once you have a Crowdin account, login and translate the software in your browser!

Localizing strings in new code requires usage of a few rules.

License

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: