However, these strings do not appear in the list and the mentioned workaround also does not make them appear. “MrGeneration” referred me to the community. Why? I have no idea as this is obviously not a duplicate and not fixed.
Thanks for looking into this. And thanks to all devs for the great Zammad tool!
I definitely think you are right and Zammad Team is wrong, this string is not configurable through the admin webinterface and the described workaround can’t be used here since this is coded into the mail template and can’t be somehow triggered in the webinterface.
You will probably have to accept that you won’t get this fixed because they obviously don’t want to fix it. They are a small team and have to select which features are worked on and such things don’t have priority. If it’s extremely important to you you could make an inquiry for a paid feature / fix, those have a higher chance to get worked on.
Or maybe this will be possible to translate once Zammad 5.1 and translations.zammad.org go live, I don’t know if the strings will be listed there. I’d wait for that before thinking about a paid inquiry.
Depends on where I should have mentioned it in your opinion.
If you’re talking about the issue:
No - the reason for that is that we want to keep repository noise as low as possible.
If I’d provide such information (even if they belong to your issue but technically do answer a technical question or are out of context) this may raise more “questions”. So I’d shoot into my own knee. I do understand that this strict dividing is not always a good thing and very confusing to new people - but in the end it does help us to focus.