Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add something about translation of attributes #384

Closed
YetAnotherGerrit opened this issue Oct 27, 2023 · 5 comments · Fixed by #398
Closed

Add something about translation of attributes #384

YetAnotherGerrit opened this issue Oct 27, 2023 · 5 comments · Fixed by #398

Comments

@YetAnotherGerrit
Copy link
Contributor

YetAnotherGerrit commented Oct 27, 2023

It is possible to translate attributes in trigger (and maybe text modules) with the following syntax:
#{t(ticket.state.name)}

This is not mentioned in the documentation yet and needs to be added.

@ralf401
Copy link
Contributor

ralf401 commented Nov 2, 2023

@YetAnotherGerrit can you explain what you mean or give an example? For the general translatability, we have a note in the admin-docs.
But you probably mean another feature, right?

@YetAnotherGerrit
Copy link
Contributor Author

When you phrase texts in text modules, trigger, scheduler, signatures you can use #{name} to include values of different attributes within. These can be translated using #{t(name)}. This is currently not mentioned in the documentation.

@ralf401 ralf401 self-assigned this Nov 8, 2023
ralf401 added a commit that referenced this issue Nov 8, 2023
@ralf401 ralf401 linked a pull request Nov 8, 2023 that will close this issue
@dominikklein
Copy link
Contributor

dominikklein commented Nov 10, 2023

But is it really for all situations working? I'm not sure about the stuff which is replaced inside the frontend (e.g. text modules or signature).

@ralf401
Copy link
Contributor

ralf401 commented Nov 10, 2023

I tried it in text modules, trigger and scheduler. I wrote that it works in these 3 areas.

@ralf401
Copy link
Contributor

ralf401 commented Nov 20, 2023

Tested it again => just working in trigger and scheduler.

Pushed changes again to PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants