Release Notes: OTRS Help Desk 3.1.13

February 19, 2013 -- 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.13.

 

Release Details

  • Release name: OTRS Help Desk 3.1.13
  • Release type: Stable, patch level release
  • Release date: February 19, 2013
 
 
 

 

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
  • Patch level release 3.1.13: Feb 19, 2013
 
 
 
 

What's New

  • Updated Russian translation, thanks to Vadim Goncharov!
  • Added new translation for Spanish (Colombia), thanks to John Edisson Ortiz Roman!
  • Updated CKEditor to version 3.6.6.
  • Updated Polish translation, thanks to Pawel @ ib.pl!

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#9162 - Setting the start day of the week for the datepicker to Sunday does not work.
  • Bug#9141 - Confused Columns in CustomerTicketSearch (ResultShort? ).
  • Bug#9146 - Signed SMIME mails with altered content shows a not clear message.
  • Bug#9145 - SMIME sign verification errors are not displayed in TicketZoom.
  • Bug#9140 - Postmaster Filter for empty subjects does not work.
  • Bug#9121 - Filenames with Unicode NFD are incorrectly reported as NFC by Main::DirectoryRead().
  • Bug#9108 - Check for opened/closed tickets not working with Ticket::SubjectFormat = Right.
  • Bug#8839 - DateChecksum followup doesn't get correctly SystemID.
  • Bug#9101 - Not possible to create dropdown with autocomplete attribute.
  • Bug#9096 - All services list is shown instead of only default services.
  • Bug#8470 - otrs.GenericAgent.pl reports: Can't open '/opt/otrs/otrs_vemco/var/tmp/CacheFileStorable/DynamicField/f3b7e10730fb6c9cab5ae0e7f7e034f3'.
  • Bug#9054 - Link Object deletes all links under certain conditions.
  • Bug#8944 - do not backup the cache.
  • Bug#9057 - Generating a PDF with bin/otrs.GenerateStats.pl produces lots of warnings.
  • Bug#8929 - Fix problems with empty ticket search results while Ticket::Frontend::AgentTicketSearch###ExtendedSearchCondition is inactive.
  • Bug#9042 - Add X-Spam-Score to Ticket.xml.
  • Bug#9047 - HistoryTicketGet caches info on disk directly.
  • Bug#8923 - Alert message shown, if parent window is reloaded while bulk action popup is open.
  • Bug#9030 - Wrong handling of Invalid YAML in Scheduler Tasks.
  • Follow-up fix for bug#8805 - Cron missing as RPM dependency on Red Hat Enterprise Linux. Changed dependency on 'anacron' to 'vixie-cron' on RHEL5.
  • Bug#9020 - Generic Ticket Connector does not support attachments with ContentType without charset.
  • Bug#8545 - Attachment download not possible if pop up of another action is open.
  • Bug#9009 - Empty Multiselect Dynamic Fields provokes an error.
  • Bug#8589 - Bulk-Action not possible for single ticket.
  • Bug#7198 - Broken repository selection width in Package Manager.
  • Bug#8457 - Error if accessing AgentTicketSearch from AgentTicketPhone in IE8.
  • Bug#8695 - Table head of Customer Ticket History does not resize on window resize.
  • Bug#8533 - Apache will not start if you use mod_perl on Fedora 16 or 17.
  • Bug#8974 - Event Based Notification does not populate REALNAME with Customer User data.

The detailed ChangeLog can be found at: http://source.otrs.org/viewvc.cgi/otrs/CHANGES?revision=1.2260.2.206&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