-
Bug
-
Resolution: Tracked Elsewhere
-
Low
-
None
-
None
-
None
-
1
-
Severity 3 - Minor
-
1
-
Issue Summary
JIRA Portfolio 3.6.0 in JIRA 8.2 custom fields name is on its translation key like below:
- rm.jpo.plan.common.baselineEnd
- rm.jpo.plan.common.baselineStart
Environment
JIRA 8.2 (Portflio 3.6)
Steps to Reproduce
- Install JIRA 8.2 with JIRA Portfolio 3.6
- Navigate to JIRA Administration > Issues > Custom Fields
- Search for the field "Target"
Expected Results
"Target End" and "Target Start" should be shown
Actual Results
Nothing will be shown because the name is set to the translation key. Searching "rm" will show the following fields:
Notes
The issue is caused by a bug affecting JIRA Core which is the platform where Portfolio is installed.
Workaround
-
- is related to
-
JRASERVER-69388 Some Jira entities created when installing applications show i18n keys instead of translated values.
- Closed
- relates to
-
JRASERVER-69388 Some Jira entities created when installing applications show i18n keys instead of translated values.
- Closed