- You can use translations to customize JEMHCloud system labels. Create an English translation with no email regexes and change the labels like 'velocity.macro.action.footer.signature'
If you're creating your own custom template, you can use this feature replacing static texts in your template for $messageUtils.getMessage("yourCompany.someKey"). You will need to create your own translation adding key=label pairs, when doing so, it's recommended to use a prefix to avoid possible key collision. Note: JEMHCloud is not able to detect missing custom keys in translations. yourCompany.someKey=The static text
- JEMHCloud uses JIRA's names when resolving field names in English. Although they are not defined in the system default, they can be translated. Have a look at the summary, issuetype, priorty, etc. keys in the Spanish example.
- Some known issues and improvements around translations are:
| Jira Legacy |
|---|
| server | JIRA (thepluginpeople.atlassian.net) |
|---|
| serverId | 31e1f342-5dce-3979-a43c-85899d565476 |
|---|
| key | JEMHC-304 |
|---|
|
, | Jira Legacy |
|---|
| server | JIRA (thepluginpeople.atlassian.net) |
|---|
| serverId | 31e1f342-5dce-3979-a43c-85899d565476 |
|---|
| key | JEMHC-306 |
|---|
|
and | Jira Legacy |
|---|
| server | JIRA (thepluginpeople.atlassian.net) |
|---|
| serverId | 31e1f342-5dce-3979-a43c-85899d565476 |
|---|
| key | JEMHC-307 |
|---|
|
|