arrow-rightautosavechatcheckmarkclosedashboardfieldsfingerprintflashhamburgerlanguagelistlocklogotypemigrateoverviewsphonerocketsearchsmileystampstarstopwatchteamtwitter

We are pleased to release Zammad 2.4.

This is also a Security Release for all previous versions and we recommend updating your installations immediately (relevant Security Advisory).

Now to the release. Besides the bugfix release Zammad 2.3.1, Zammad 2.2.2 we also release the new Zammad 2.4.0 with the following major improvements.

Feature #1: Autocompletion when replying

When creating tickets, the customer could already be searched for by auto-completion. If you wanted to forward an e-mail or take other people into the "Cc" when replying, you previously had to enter the complete e-mail address yourself.

This is now a thing of the past. As of today, known addresses can become recipients when forwarding or replying via auto-completion.

feature-autocomplete

Feature #2: Generic Clone in the admin area

It happens more often that similar objects (e.g. users, groups or signatures) have to be created in the admin area. This is annoying and no fun - and is now a thing of the past. From now on objects with all attributes can be duplicated in the admin area.

feature-admin-clone

Feature #3: RichText - Adjusting the image size

Up to now, the size of an image could only be adjusted in a few browsers, since this was not supported by everyone.

This has not stopped us from making it available to all browsers. Have fun with that.

feature-richtext-image-adjustment

Feature #4: REST API - Requests on behalf of another user

With the Zammad REST API you can quickly and easily perform actions on tickets. Many users use this function for integration (e.g. integrating a customer's tickets into their own customer portal). However, write actions were logged in the name of the executing API user and not the name of the user who executed the action itself in the customer portal.

Using an "X-On-Behalf-Of" header, actions can now be performed in Zammad that are to take place on behalf of another user.

Detailed information can be found in the API documentation at the following URL:

https://docs.zammad.org/en/latest/api-intro.html#example-curl-request-on-behalf-of-a-different-user

Breaking Change #1: Authorization to Edit Agents/Administrators

In Zammad, up to version 2.4, it was possible (unintentionally) as an agent to edit administrator accounts and save attributes such as Active or Email modified. These actions have now been "restricted".

A detailed overview of the possible actions can be found in the Zammad < 2.4 matrix.

Matrices:

Zammad >= 2.4

accessed admin.user sub admin without admin.user agent same customer same organization different customer
admin read, change, delete read read - - none
agent read, change, delete read read - - none
customer read, change, delete read read, change read read none

Zammad < 2.4

accessed admin.user sub admin without admin.user agent same customer same organization different customer
admin read, change, delete none read, change, delete - - none
agent read, change, delete none read, change, delete - - none
customer read, change, delete none read, change, delete read, change, delete none none

Downloads

Alle weitere Verbesserungen finden Sie im Changelog.

Download Zammad 2.4.0

Changelog (2018-03-29)

Source code

Packages

Download Zammad 2.3.1

Changelog (2018-03-29)

Source code

Packages

Download Zammad 2.2.2

Changelog (2018-03-29)

Source code

Packages

Upgrade

Information about upgrading a Zammad installation can be found here:

Your Zammad team!