Newer
Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
osTicket v1.7.1
===============
### Bugfixes
* Properly reject attachments submitted via the API (#668)
* Correctly support the "Use Reply-To" in ticket filters (#669)
* Don't log users out after changing username or email address (#684)
* Don't leak private FAQ article titles (#683)
osTicket v1.7.1-rc1
===================
### Enhancements
* Custom logos and site pages (#604, #632, #616)
* Password reset link (#638)
* Export and import feature. Useful for migrations and backups. (#626)
* Use your email address as your username for logins (#631)
* SLA's can be marked *transient*. Tickets with a transient SLA will
change to the SLA of the new department or help-topic when transferred
or edited.
* Support installation on MySQL and MariaDB clusters. Use default storage
engine and don't assume predictable auto-increment values (#568, #621)
### Geeky Stuff
* mysqli support for PHP5+
* SSL support for database connections
* Namespaced configuration. This greatly simplifies the process of adding
* new configurable item (#564)
* Add signals API. A simple event hooking mechanism to allow for
* extensibility (#577)
* Add deployment command-line script (#586)
* Allow XHTML editing in the nicEditor (#615)
* Allow parallel database migration streams (#563) -- paves the way for
*extensions*
* Use row-based email templates (#604) -- simplifies the process of adding
new email message templates (think *extensions*)
* Support fetching from email boxes with aliased email addresses (#663)
* Introduce new crypto library that provides failsafe encryption for email
passwords (#651)
### Bugfixes
* Several typos in code and messages (#617, #618, #644, #660)
* Fix several upgrader bugs (#548, #619)
* Fix install fail on some Windows platforms (#570)
* Fix several issues in the command-line management (#580)
* Make room for command-line installation of osTicket (#581)
* *regression* Fix corrupted attachment downloads (#579, #583)
* Fix truncated attachment downloads when `zlib.output_compression` is
enabled (#596)
* Disable cron activities when upgrade is pending (#594)
* Provide failsafe encoding for improperly-formatted emails (#601)
* Fix corrupted email attachments processed via `pipe.php` (#607)
* Fix discarding of poorly encoded base64 emails (#624)
* Support MariaDB 10.0+ (#630)
* Properly trim ticket email and name fields (#600)
* Fix truncated text from text/plain emails and web interface posts (#652)
* Add **Assigned To** and other fields to ticket view export (#646)
* *regression* Fix attachment migration (#648)
* Display correct staff notes (#588)
* Display correct auto-response email for departments (#575)
* Fix login form ("Authentication Required") loop (#653)
* Ensure email message-id is fetched correctly (#664)
* Ensure X-Forwarded-For header does not have leading or trailing
whitespace (#665)
### Performance
* Only fetch configuration for multifile upload if necessary (#637)
* Don't use sessions on the API (#623)
* *regression* Avoid an extra query per request to fetch schema signature
(#658)
New stuff in 1.7.0
====================
* Bug fixes from rc6
New stuff in 1.7-rc6
====================
* Bug fixes and enhancements from rc5
New stuff in 1.7-rc5
====================
* Bug fixes from rc4
New stuff in 1.7-rc4
====================
* Bug fixes from rc3
New stuff in 1.7-rc3
====================
* Bug fixes from rc2
* Canned auto-reply template
* Modal dialogs
* PEAR packages upgrade
New stuff in 1.7-rc2
====================
* Bug fixes from rc1
* Nested help topics support
New stuff in 1.7-rc1
====================
* Upgrade support for osTicket 1.6-rc1 and later
* Multi-file upload support -- more than one file (configurable) can be
uploaded with new messages, replies, and internal notes via the web
interface
* Department/Group access feature allowing members of a group access to a
department. Staff members are members of a (primary) group, and that
group can be granted access to one or more departments, granting the
associated staff access to departments other than their primary
department.
* Email filters can specify a canned auto-response
* Support inline attachments for fetched email
* Dashboard reports for ticket system activity and statistics
* PDF print / export for tickets (staff pages only)
New stuff in 1.7-dpr3
======================
* Advanced search on tickets page
* Ticket thread -- revised ticket message storage model for greater
flexability
* New database upgrade system allowing for continuous updates to the
database model. This will greatly simplify the process of making
modifications to the osTicket database.
New stuff in 1.7-dpr2
======================
* Autocomplete for ticket search box (emails and ticket numbers typeahead)
* Redesigned staff login page
* Warning when leaving unsaved changes in admin and staff settings pages
* Auto change admin settings pages when selecting a new page from the
drop-down list
* Create a ticket in one click from the staff panel
* Preview ticket from the search results
* Export tickets to CSV file
New Features in 1.7
===================
Version 1.7 includes several new features
As an upgrade from email banning (which is still supported), ticket filters
allow for matching incoming email in the subject line and message body. For
matching emails, the administrator has the ability to automatically route
tickets:
* To a specific department, staff member, and/or team
* Automatically assign ticket priority and/or service-level-agreement
* Disable ticket auto-responses
Tickets filters are also applied to tickets submitted via all ticket
interfaces, including the API, email, staff and client web interfaces. And,
as a bonus, the filters can be configured to target only a single interface.
So an administrator could, for instance, target tickets received via email
from a particular domain.
Canned Attachments
------------------
Attach files to your canned responses. These attachments are automatically
attached to the ticket thread along with the canned response. The
attachments are not duplicated in the database and therefore use virtually
no space.
Database-backed Attachments
---------------------------
No more crazy security-related configuration to your host server in order to
support attachments. Attachments are now quietly stored in the database. The
upgrade migration will automatically port attachments from the previous
locations into the database.
Service Level Agreements
------------------------
Service level agreements allow for a configurable grace period based on the
department or help topic associated with the ticket. A default SLA is
provided, and a due date can be set to override the grace period of the SLA
for a ticket.
Client-side Knowledgebase
-------------------------
Manage a searchable help document portal for your users
Flashy reports of ticket system activity as well as exportable ticket system
statistics, allowing for easy report generation from office spreadsheet
applications.
Ticket Export
-------------
Convert the ticket thread to a printed format for long term storage. The
ticket view page now supports a print feature, which will render the ticket
as a PDF document.
API
---
Interface with osTicket via HTTP requests. Starting with version 1.7,
tickets are createable by submitting an HTTP POST request to either
/api/tickets.xml
/api/tickets.json
The API can also be used to pipe emails into the osTicket system. Use the
included `automail.php` or `automail.pl` script to pipe emails to the
system, or post raw email messages directly to
/api/tickets.email
Use of the API requires an API key, which can be created and configured in
the admin panel of the support system.
For technical details, please refer to [API Docs] (setup/doc/api.md).
Geeky New Features
==================
Unicode
-------
Better and more consistent international text handling
Flexible Template Variables
---------------------------
Template variables have been redesigned to be more flexible. They have been
integrated into the respective object classes so that an object as well as
its properties can be represented in template variables. For instance
%{ticket.staff.name}