Trigger based content from objects should be translated

Feature requests Interesting for future roadmap
1

Title: Trigger based content from objects should be translated

Usecase environment:

  • average concurrent agent count? 2
  • average tickets a day? 15
  • what roles/people are involved? Agents and customers

What is the idea or pain point:

  • Translation of trigger based content
  • why is it not solvable with Zammad standard?
    Because trigger based content is not beeing translated

Expectation (not solution):

  • Trigger based content should be translated into the sysem language.
1 Like
2

Related post: Community feedback: translation of variables

1 Like
3

@R2D2 maybe you are able to add some use cases about the problem. So that it’s easier to go forward.

4

The use case is that I will send the customer an email and that email contains the status of the ticket like this:

Status: #{ticket.state.name}

Now the German customer read “new” instead of “neu” or “open” instead of “offen”. The function that replaces that variable should be expanded to translate it before replacing.

5

In dem Use-Case wäre die System-Sprache Englisch?

6

Nein, bei mir ist die Systemsprache Deutsch, aber der Kunde bekommt den Status in Englisch, obwohl er im UI in Deutsch angezeigt wird.

7

I don’t mean the current user language, I mean the following setting: zammad run rails r "pp Setting.get('locale_default')"

8

The result is “de-de”.

9

Please use the english language. This is a english speaking board.