Versions Compared

Key

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

While eWhile the app automatically translates most of the places where "epic" is found across Jira, there are certain places like custom fields and issue types that are locked in Jira by default as this is very serious change and could cause Jira to break if done by mistake. Therefore, the configuration for these few fields should be done manually. 

...

  1. Log into your Jira as Admin.
  2. In the cog wheel menu, go to Add-ons.
  3. In the SAFE FEATURE 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 Link
    2. Epic Name 
    3. Epic Status
    4. Epic Color
       
    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.



  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 Add-ons > Configuration and lock the fields again to prevent erroneous field modification.Reboot Jira instance. After you lock the fields, Jira performs cache clearing, and you should be able to have the functionality ready.
Note

If you are using Jira Data Center, you might also need to reboot your Jira instances. No additional actions necessary if you are on Jira server.
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.