...
- Log into your Jira as Admin.
- Go to Jira Administration > Manage apps.
- In the SAFE TRANSLATOR section, click Configuration.
Unlock custom fields that are related to epics by turning the switch.
- Go to Administration > Issues > Custom fields.
- Click Translate for the following custom fields and input new values in the Field Name for each field.
- Epic LinkColor
- Epic Name Link
- Epic StatusName
- Epic ColorStatus
Warning title Warning Do not click Edit, click Translate to change how the field names look.
If you edit the fields, you will have the JQL updated as well, but most likely will face consequences during Jira update that will lead to broken data. You can only choose to do so if you never intend to upgrade Jira again or can be 100% sure to set the same field names and issue types before Jira update but we still strongly recommend against it.
Go to Administration > Issues > Issue types and translate the Epic issue type.
Warning Do not edit the Epic name to change it to Feature - only use the translate functionality.
- Go to the app configuration page and lock the fields again to prevent erroneous field modification.
- Clear cache.
- If you use Jira server
- for plugin version 2.0.0 and above - click the Clear button to trigger cache clearing.
- for the previous plugin versions - no additional actions necessary. After you lock the fields, Jira performs cache clearing, and you should be able to have the functionality ready.
- If you are using Jira Data Center
- for plugin v2.0.0 and above - go to each Jira node and click the Clear button to clear the cached names of the custom fields and issue types.
- for plugin versions below 2.0.0 - reboot your Jira instances. Jira reboot is necessary for clearing the cached names of the custom fields and issue types. As you might notice, after translation it still appears not translated at some places, and a reboot fixes it.
- If you use Jira server
...