Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Notifications sent to email addresses matching the French regexes (domains) will be in French.

Translation of Values

Allowed values in some fields are static. Examples of these fields are issue type (Bug, Task, New Feature), priority (Major, Critical, Blocker), etc. As you can see, the labels are in English as JIRA provides them.  JEMHCloud allows you to localize these values for notification using the translations. 

Although some fields are user provided, their values are fairly static and you may want to translate them. Example of these fields are Components, Labels, custom check-boxes or radio buttons, custom selects, etc. 

The key of a value translation follows the pattern:

<fieldId>.value.<value>=The translation of <value>

Examples are:

No Format
priority.value.Major=Importante
issuetype.value.Task=Tarea
issuetype.value.New\u0020Feature=Nueva Funcionalidad
components.value.My\u0020Component=Mi Componente
customfield_10100.value.TheValue=El Valor
....

Spaces are not allowed in keys and they need to be replaced with \u0020

Although the allowed keys depend on your JIRA configuration, the basic set of keys to translate values is:

No Format
issuetype.value.Improvement=
issuetype.value.Task=
issuetype.value.Sub-task=
issuetype.value.New\u0020Feature=
issuetype.value.Bug=
issuetype.value.Improvement=
priority.value.Blocker=
priority.value.Critical=
priority.value.Major=
priority.value.Minor=
priority.value.Trivial=
status.value.Open=
status.value.In\u0020Progress=
status.value.Reopened=
status.value.Resolved=
status.value.Closed=
status.value.To\u0020Do=
status.value.In\u0020Review=
status.value.Done=

It's user job to maintain value keys and their translations. JEMHCloud team cannot known all the possible values and it cannot translate them to every language.

 

JIRA (thepluginpeople.atlassian.net)serverId
  • Info
    • 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
    server31e1f342-5dce-3979-a43c-85899d565476
    keyJEMHC-304
    Jira Legacy
    serverJIRA (thepluginpeople.atlassian.net)
    serverId31e1f342-5dce-3979-a43c-85899d565476
    keyJEMHC-306
  • Jira Legacy
    serverJIRA (thepluginpeople.atlassian.net)
    serverId31e1f342-5dce-3979-a43c-85899d565476
    keyJEMHC-307
  • Filter by label (Content by label)
    showLabelsfalse
    max5
    spacesJEMHC
    showSpacefalse
    sortmodifiedshowSpacefalse
    reversetrue
    typepage
    labelsjemhc template translation localization

    ...