Versions Compared

Key

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

...

  1. Log into your Jira as Admin.
  2. Go to Jira Administration > Manage apps.
  3. In the SAFE TRANSLATOR section, click Configuration.
  4. Unlock custom fields that are related to epics by turning the switch.



  5. Go to Administration > Issues > Custom fields.


     
  6. Click Translate for the following custom fields and input new values in the Field Name for each field.
    1. Epic Color
    2. Epic Link 
    3. Epic Name
    4. Epic Status
       
    Warning
    titleWarning

    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.





    Note

    Note that the Translate dialog contains the locale. The translations are implemented for the English locale that is selected on this screen.


  7. 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.




  8. Go to the app configuration page and lock the fields again to prevent erroneous field modification.
  9. 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. 


Note
titleNotes from May 28 call with MSNote

After you configure the plugin, the word "Epic" will still be shown on the Admin pages of the custom fields and issue types. This is because Jira works in a different way for user and admin pages / screens. Thus, the translation that you apply will be shown on the user UI, but the epic related fields will still be shown with the word "epic" for the Admin pages / screens. This is a limitation of Jira, and at the moment we cannot work around this. But in case the way Jira works changes, we will be able to show "feature" on the Admin pages as well.

...