The software defines at least three contexts for the phrase "Open"

  * The name of a ticket queue (Open tickets)
  * A status of a ticket (Open / Closed)
  * An action to be performed (Open a ticket)

References:
(Crowdin login required)
http://i18n.osticket.com/translate/osticket-official/148/enus-de#2915

Multilanguage Support via gettext

- added gettext encapsulations to all texts i thought necessary
- added fallback function for the case that the gettext extension isn't loaded
- added browser language detection
- added gettext to the list of optional extensions in setup
- rewritten some of the texts to use sprintf instead of appending strings
- added german translation file
- removed mark_overdue-confirm from cannedresponses.inc.php

extend multi language support and a fex fixes

- Better detection of translation files
- Added functionality to redirect language codes (see redirecting
language codes)
- Ticket Status can be translated
- The Datepicker can be translated
- Extended functionality of 'testlang.php' to show what language code is
used to translate

Forgotten to apply a patch from RC5 to RC6

- Forgotten to change $var to $vars in line 380 of class.mailfetch.php
- Removed unneeded comment

Added php_gettext as primary translation engine

- Added php_gettext support (thanks to Danilo Segan and Steven
Armstrong)
- php_gettext is now the primary translation engine
- Extended language detection functionality

Add error/misconfiguration checks and fix undefined variables

If the advanced search dialog is up, avoid refreshing the page

- Proofread large portion of help tips.
- Implement help tip links in YAML files.
- Fix GUI spacing of some elements.
- Add <label> tags to a few form elements.

This will simplify where PJAX needs to be disabled by simply including the
navigation as part of the PJAX response.

(regardless of the source)

The warning was meant to be humorous but apparently the world has no sense
of humor.

Staff uploaded files, on new ticket, were getting attached to message instead of
response.

The warning was meant to be humorous but apparently the world has no sense
of humor.

User got emailed reply even when staff selected  -Do Not Email Reply-

The concept of extid is being retired to pave-way for customizatable ticket
numbers.

Unpack user data for filtering purposes for staff created tickets

- Remove Client form
- Provide name and email fields for cases where use is not selected (JS
issues)

Add ability to change ticket owner on ticket view
Add get last updated date to user class

Before, the draft was only cleaned up when progress on the ticket was
tracked with the reply box.

Only clean note drafts unless the ticket is being closed.

Including adding support to the TCL uninitialized variable reader to ignore
class-static variable access as well as detect inline functions and their
closure arguments.