Some Jira entities created when installing applications show i18n keys instead of translated values.

Issue Summary

Jira locked Development field name shows i18n key as it is. Other entities can be affected:

• custom field name and description (table: customfield)
• issue type name and description (table: issuetype)
• field configuration scheme name (table: fieldconfigscheme)
• field configuration name (table: fieldconfiguration)
• field layout item description (table: fieldlayoutitem)
• project role name and description (table: projectrole)
• search request query (table: searchrequest)

Environment

• Jira 8.2.0
• Not reproduced 7.13.0, 8.1.0

Steps to Reproduce

1. Build Jira with installer
2. Move Jira Administration > Issues > Custom fields
3. Check locked "Development" field

Expected Results

Field name show "Development".
Field description show "Development Summary Field for Jira Software use only".

Actual Results

Field name show "devstatus.customfield.development.name".
Field description show "devstatus.customfield.development.desc".

Notes

• When search issue with development field, need to use i18n key.

  devstatus.customfield.development.name[pullrequests].open > 0

• Approvals, Organizations, Customer Request Type Custom Field, Request Participants in Jira Service Desk field also have same issue.
  
• JIRA Portfolio Custom Fields also affected by this
  

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available