Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

osTicket v1.8 (Rumors) Preview Released

We’re stoked to announce the availability of osTicket v1.8-DPR (Developer Preview Release).

The pre-release will strictly be for developers and enthusiasts to peek into, troubleshoot and help us test the upcoming release. We plan on using the feedback to shape the upcoming release of osTicket. It is not yet recommended for production environments nor recommended for upgrading existing installations.

What’s new?

osTicket v1.8 include two major feature additions to osTicket. Download and install the up-and-coming version today and join in the development process. We're trying harder to get the community involved in the feature review and feedback process!

[h=2]Rich Text (HTML) Support[/h]
As an option, enabled by default, osTicket can now process HTML email and allows for rich text markup in most long-answer boxes across the system, including staff replies and internal notes posted to the ticket thread. To keep the feature consistent throughout, canned responses and email templates also sport an HTML theme now.

Custom Fields and Forms

The data collected from your users when they fill out the ticket form is now customizable. You can now ask any information relevant to your business practice, and can customize the type of input show from the user. Currently, short and long answer fields, drop-down lists, checkboxes, date and time, and phone number fields are available. Each field is configurable and can be setup according to your liking. Fields can also be marked as required, whose input is required to submit the ticket, and internal, whose input is not visible to the end user.

That’s not all! For detail information about the new features refer to the blog post

[HR][/HR]
Once again, osTicket v1.8-DPR is pre-release software, in active development, that may be substantially changed before it's packaged for public release. It is NOT recommended for production environments nor recommended for upgrading existing installations

To give it a go, please refer to installation guide on GitHub.

We’re excited and look forward to your participation.

osTicket Team

Comments

  • edited October 2013
    Hey Jared,

    tickets.inc.php is using static tables

    ' LEFT JOIN ost_form_entry entry ON entry.object_type=\'T\'
    and entry.object_id=ticket.ticket_id'.
    ' LEFT JOIN ost_form_entry_values ans ON ans.entry_id = entry.id'.
    ' LEFT JOIN ost_form_field field ON field.id=ans.field_id';

    Just thought id post it if you hadnt picked up on it yet.

    Also New Message Auto-response template needs a default subject.
  • edited October 2013
    Installed with xampp. I'm getting this:

    Strict Standards: Non-static method osTicket::get_root_path() should not be called statically in C:\xampp\htdocs\ticketsys\bootstrap.php on line 226

    Strict Standards: Only variables should be passed by reference in C:\xampp\htdocs\ticketsys\include\class.osticket.p hp on line 388

    Strict Standards: Non-static method Bootstrap::init() should not be called statically in C:\xampp\htdocs\ticketsys\bootstrap.php on line 229

    & I certainly hope I'm not being special.
  • edited October 2013
    Thank you very much Jared. It works. I am really excited about OSticket 8. Custom fields are what I was looking for :) and I am glad you guys will add this feature.
    I just have a question. What about feature requests? I am interesting in adding some of the custom fields I created into the View ticket form. Is there a way to do that? Should I post this on GitHub too?

    in ticket-view.inc.php, there is a section where you define vars


    //Get the goodies.
    $dept = $ticket->getDept(); //Dept
    $staff = $ticket->getStaff(); //Assigned or closed by..
    $team = $ticket->getTeam(); //Assigned team.
    $sla = $ticket->getSLA();
    $lock = $ticket->getLock(); //Ticket lock obj
    $id = $ticket->getId(); //Ticket ID.


    So maybe I would have to define a new var to get the value for my custom filed, ie $country, but I do not how I should get my data from my custom field.


    Thanks again and I will continue testing this beta version :) and I will report any bug I can find


    Greetings,

    Pavel
  • edited November 2013
    Hiya!

    How long till you go live with 1.8? I have 1.7.3 now, but I really like the HTML email modification, before taking it to our users. I am very happy I found this ticketing system :)
  • edited November 2013
    I have this (v1.8.0-rc1-3-g293fa74) installed and like all the updates, but having two issues:

    1) Important: I cannot tell how I can include the custom fields when creating a ticket through API. From the code it looks like its supported, but there has to be some special formatting needed. I am trying to use the XML API (api/tickets.xml) to submit, and since my custom fields are required, the call always fails.

    2) Less Important: From what I can tell, the HTML email is causing issues with the parsing of the response. I had to modify the Reply Separator Tag to even get this to work and now the responses include an extra line like:

    On Nov 7, 2013, at 10:29 PM, "Support" <</font>support@acme.com> wrote:

    any suggestions?
  • @jace.larson88 I am getting the exact same errors as you, downloaded 1.8-latest today. Did you manage to fix this or figure out whats causing it ?
This discussion has been closed.