Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-69388

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

XMLWordPrintable

      Update:

      Both 8.2.4 and 8.3.0 could still be affected by this bug.
      The following paths were fixed in 8.2.4/8.3.0:

      • installing an applications and apps (plugins) on a running JIRA Core (8.2.4/8.3.0) 
      • installing JSD with the installer without dbconfig.xml (8.2.4/8.3.0) 

      The following installation could still lead to experiencing this bug:

      • installing JSD with the installer with an existing dbconfig.xml 

      Planning to release 8.3.1 with:

      • fix for this bug
      • upgrade task fixing broken installation (internal Jira Core DB tables) which experienced this problem

      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

        1. image-2019-06-20-16-12-45-228.png
          image-2019-06-20-16-12-45-228.png
          27 kB
        2. jpo.png
          jpo.png
          30 kB
        3. portfolio.png
          portfolio.png
          236 kB
        4. Screen Shot 2019-05-24 at 18.05.06.png
          Screen Shot 2019-05-24 at 18.05.06.png
          183 kB

              mswinarski Maciej Swinarski (Inactive)
              tsuzuki@atlassian.com Tomoko Suzuki
              Votes:
              77 Vote for this issue
              Watchers:
              87 Start watching this issue

                Created:
                Updated:
                Resolved: