Release Notes: OTRS Help Desk 3.1.12

December 11, 2012 -- OTRS, the world's leading provider of open source Help Desk and ITIL® V3 compliant IT Service Management (ITSM) solutions, today announces the patch level release of OTRS Help Desk 3.1.12.

 

Release Details

  • Release name: OTRS Help Desk 3.1.12
  • Release type: Stable, patch level release
  • Release date: December 11, 2012
 
 
 

 

Release Schedule

  • Stable release: Feb 14, 2012
  • Patch level release 3.1.2: Mar 6, 2012
  • Patch level release 3.1.3: Mar 29, 2012
  • Patch level release 3.1.4: Apr 24, 2012
  • Patch level release 3.1.5: May 15, 2012
  • Patch level release 3.1.6: Jun 05, 2012
  • Patch level release 3.1.7: Jun 26, 2012
  • Patch level release 3.1.8: Aug 07, 2012
  • Patch level release 3.1.9: Aug 22, 2012
  • Patch level release 3.1.10: Aug 30, 2012
  • Patch level release 3.1.11: Oct 16, 2012
  • Patch level release 3.1.12: Dec 11, 2012
 
 
 
 

What's New

  • Removed auto cleanup of expired sessions in CreateSessionID() to improve the scalability of the whole system.
  • Updated Polish translation, thanks to Pawel!
  • Improved caching for Services and Service Lists.

Important for Upgrading

  • Upgrading from OTRS 3.1.x: Make sure you run bin/otrs.RebuildConfig.pl after the upgrade so that the configuration is refreshed. Otherwise the system may not work. Please note that for upgrades from 3.1.0.beta1 or 3.1.0.beta2, an additional database upgrade step is required (see UPGRADING)!
  • If you upgrade from a version before 3.1.6 AND use OpenSSL 1.x to encrypt/sign your emails with S/MIME, you need to refresh the password and certificate file names (see UPGRADING).
  • Upgrading from OTRS 3.0.x: Please read the UPGRADING and INSTALL files for detailed instructions.

Bug Fixes

  • Bug#8933 - ArticleStorageInit permission check problem.
  • Bug#8763 - Please add charset conversion for customer companies.
  • Bug#1970 - Email attachments of type .msg (Outlook-Message) are converted.
  • Bug#8955 - Init script might fail on SUSE.
  • Bug#8936 - Ticket close date is empty when ticket is created in closed state.
  • Bug#8937 - "$" should be escaped in interpolated strings when javascript is meant.
  • Bug#8919 - Customer interface search results: ticket can only be accessed via ticket number and subject.
  • Bug#8850 - CustomerTicketOverview - MouseOver Age isn't always correct.
  • Bug#8868 - Event Based Notification problem saving 'text' Dynamic Fields.
  • Bug#8914 - Syntax error in hash loop in TicketGet operation.
  • Bug#8749 - CustomerFrontend: missing dynamicfield in search results.
  • Bug#8873 - Bad example of customization of "static" dynamic fields in AgentTicketOverviewSmall.
  • Bug#8791 - IMAPTLS fails with some Microsoft Exchange servers.
  • Bug#8841 - Search for Dynamic Fields shows all tickets (on "enter" key pressed).
  • Bug#8861 - Ticket History overlaid calender choice function.
  • Bug#8862 - GI debugger GUI does not show SOAP XML tags correctly.
  • Bug#8566 - Cannot download attachment if filename has character #.
  • Bug#8833 - Article table in TicketZoom does not scroll correctly.
  • Bug#8673 - Richtext-Editor popups broken on Customer-Interface.
  • Bug#8859 - Package upgrade does not work if an installed testpackage should be upgraded with a newer regular package.
  • Bug#8678 - 'WidgetAction Toggle' is always shown as 'Expanded' when nesting elements
  • Bug#8378 - Validation fails if the ID of the element contains a dot (.) or a colon (:)
  • Bug#8847 - Inline PGP message description routine does not add any info, thanks to IB Development Team.
  • Bug#8848 - AgentTicketEmail does not preserve PGP Signatures set if attachment is added.
  • Bug#8149 - Wrong handling of subject when SubjectFormat=right.
  • Bug#8820 - Service rcotrs restart fails because a race condition happens.
  • Bug#8819 - Syntax error (stop crontab command) in SuSE rc script.
  • Bug#8667 - TicketSplit does not use QueueID of old Ticket for ACL Checking.
  • Bug#8780 - 508 Compliance: Text descriptions of "Responsible Tickets" and "Locked Tickets" links are insufficient for screen reader users.
  • Bug#8812 - Encrypted email doesn't see properly in Outlook.
  • Bug#8214 - OTRS Init script on Red Hat fails to check scheduler.
  • Bug#8850 - Cron missing as RPM dependency on Red Hat Enterprise Linux.
  • Bug#7274 - Ticket QueueView sorts by priority on first page but subsequent pages sort incorrectly by Age.
  • Bug#8792 - TriggerEscalationStopEvents logs as loglevel 'error'.
  • Bug#8743 - AgentTicketCompose.pm creates To, CC, BCC filelds without spaces after comma.
  • Bug#8606 - Escalation notifications should not be sent to agents who are set out-of-office.
  • Bug#8740 - backup.pl: insufficient handling of system() return values.
  • Bug#8622 - Storing a new GI Invoker or Operation with an existing name doesn't complain anything.
  • Bug#8770 - AJAX Removes Default Options (follow-up fix).

The detailed ChangeLog can be found at: http://source.otrs.org/viewvc.cgi/otrs/CHANGES?revision=1.2260.2.169&view=markup.

Browser Support

  • JavaScript is required to use the agent interface.
  • The following browsers are not supported:
    • Microsoft Internet Explorer before version 8
    • Firefox before version 3
    • All versions of Netscape
  • We recommend to always use the latest version of your browser, to benefit from the best possible JavaScript and rendering performance.
  • Dramatic performance differences may occur based on the use of different browsers, especially in large system environments. We are glad to consult you on this matter.

Supported Encodings

  • OTRS 3.1 supports only UTF-8 as internal character set. Non-UTF-8 installations of OTRS must switch to UTF-8.

Download

Download the latest release with your OTRS-ID – Your personal all-round account

Your benefits:

  • free promotion specials
  • free access to our knowledge database to solve problems
  • stay informed with our OTRS-Newsletter and manage your newsletter subscription
  • contact us more easily and keep track of your requests


If you already have login information to our OTRS-Portal, you also have an OTRS-ID (email-address). Please, log in as usual https://portal.otrs.com/otrs/customer.pl  You can find the current releases in the section "Download“ If your password is not accepted, please use the „Forgot password“-link, so we can send you a new password.

If you do not have an OTRS-ID, you can register for free at https://portal.otrs.com/otrs/customer.pl#Signup

If you don’t want to use the benefits of an OTRS-ID, you may proceed with the Public Download

 

Professional Services

OTRS Group, the source code owner, provides world-wide enterprise support, consulting and engineering including process design, implementation, customization, application support, and fully managed service.

Community Support

Leverage the various OTRS Community sources to get involved:

 
 

What's new in OTRS 3.1