Make the tags translatable

Feature requests
1

1) What is your original issue/pain point you want to solve?

A common object is used by multiple languages. Users and administrators must assign the relevant tags. They must do this in all languages.

2) Which are one or two concrete situations where this problem hurts the most?

Imagine a company using the Zammad system to provide an Portal for its employees in different countries. Users can access Zammad in their preferred language. When creating a common knowledge base article, the editor has to assign too many tags because tags are not translatable. For example, if the company has subsidiaries in Hungary, Slovakia, Romania, the Czech Republic, and Ukraine, and the article is relevant to four tags, the editor must assign 20 tags to the article. In this case, users see too many tags, and it is difficult to find which ones are related to their preferred language. The user experience is negatively impacted by the presence of numerous “non-relevant language” tags, which detract from the visualisation.

3) Why is it not solvable with the Zammad standard?

Tags are not allowed to translate.

4) What is your expectation/what do you want to achieve?

If Zammad supports the translation of tags, the system will be more valuable and operational. With translatable tags, users can use common tags, and the system can provide more relevant content when someone searches based on a tag.

Thank you and have fun.

2

Multi Tree Selects can replace tags in most cases and are translatable. Could you please describe the use case that requires you to use tags instead?

3

Hi, thank you for the tip! I want to use tags because custom fields are specific to one object. As I understand it, tags are “interoperability” fields that store information for multiple objects. For instance, if I assign the tag “data privacy” to a knowledge base article and to a ticket, Zammad can list both the KB article and the ticket in the result list when a user searches for “data privacy.” (E.g. the user clicks on the tag, all the relevant objects are listed.)

If I understand custom fields correctly, this interoperability would not be possible.