-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
8.2.0, 8.2.1, 8.3.0, 8.2.3, 8.2.4
-
8.02
-
26
-
Severity 2 - Major
-
529
-
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
- Build Jira with installer
- Move Jira Administration > Issues > Custom fields
- 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
- causes
-
-
- Closed
-
-
JSMDC-4097 You do not have permission to view this issue
- details
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
![[JIRA Server (Bulldog)] Story - Created by Jira Software - do not edit or delete. Issue type for a user story.](https://bulldog.internal.atlassian.com/images/icons/issuetypes/story.svg "[JIRA Server (Bulldog)] Story - Created by Jira Software - do not edit or delete. Issue type for a user story.")
DELTA-817
You do not have permission to view this issue
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- duplicates
-
JSEV-2629 Loading...
- is caused by
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRASERVER-69388] Some Jira entities created when installing applications show i18n keys instead of translated values.
Hi, atlassian_support1 Thank you for letting now about the JSW "Development" status still being affected. I have created another issue to specifically track this problem: https://jira.atlassian.com/browse/JSWSERVER-20164
Hi atlassian_support1, could you clarify what is the problem exactly. In 8.2.4 we have reverted the broken contract between plugins/apps and Jira Core, where Jira Core internal state (like i18n cache) should reflect the current state of the plugin system when plugins receive PluginEnabledEvent. On a fresh installation of Jira 8.2.4 with JSW this problem should be fixed. Could you describe what problem you are experiencing?
also affects JSW 8.2.4 (build a new instance by 64-bit linux installer)...
does this fix include in 8.2.4?
Hello webadmin7,
We’ve just released Jira 8.2.4. This version will prevent the issue from affecting new data. However, the upgrade won’t fix the already existing problems. We are working on a solution for this as well.
Cheers
Is there a possible ETA on 8.2.4 or 8.3.0? This is critical to our upgrade schedule.
The problem affects any app that creates custom fields at installation time. This includes Jira Software and/or Service Desk if they are installed as separate apps. Problem is not visible when upgrading with existing apps. It is also not visible when installing bundled Core+Software or Core+Service Desk.
I did reproduce it with 8.3m1 on custom fields section. See related issue @sergey
Sorry, I dont understand. I update to 8.2.2 but dont see that bug. How that reproduce?
KB with details about the upgrade process: https://confluence.atlassian.com/jirakb/custom-field-names-shows-message-keys-instead-of-values-jraserver-69388-975028931.html