-
Bug
-
Resolution: Fixed
-
High
-
4.20.14
-
8
-
Severity 3 - Minor
-
15
-
Issue Summary
Some insight placeholders are not available in the version of Insight/Assets for Jira 8.20.14 / JSM 4.20.14. For instance:
rlabs.insight.i18n.plugin.configure.portal.single.default=Search for an object
rlabs.insight.i18n.plugin.configure.portal.multiple.default=Search for objects
The above are all available (and all the placeholders in the new version also correctly refer to "Assets" as opposed to "Insight") in Jira 9.3.1 / JSM 5.3.1
This is reproducible on Data Center.
The affected Insight jar is insight-9.1.13-QR-0023.jar.
The problem is resolved in insight-10.0.16-QR-0022.jar.
Steps to Reproduce
- Install JSM 4.20.14
- Set up an Insight object field on case creation, visible from the portal (single or multiple, it doesn't matter)
- Check the portal to see if the placeholder correctly shows for the Insight
Expected Results
The placeholder correctly translates to the corresponding entry, which disappears when clicked:
- "Search for an object"
- "Search for objects"
Actual Results
The placeholders' key is displayed instead:
- rlabs.insight.i18n.plugin.configure.portal.single.default
- rlabs.insight.i18n.plugin.configure.portal.multiple.default
Workaround
- Find and unzip the insight jar file (insight-9.1.13-QR-0023_1666247918000.jar)
- In the resulting folder, look for file properties/i18n.properties
- Add the following entries:
rlabs.insight.i18n.plugin.configure.portal.single.default=Search for an object rlabs.insight.i18n.plugin.configure.portal.multiple.default=Search for objects
- Repackage the archive (i.e. zip the files again, replace the extension with "jar")
- Install from the frontend (via the "Manage apps" page) or alternatively, find and replace the jar file in the shared drive & do a rolling restart of the nodes.
Form Name |
---|
[JSDSERVER-12149] Jira 8.20.14 breaks Insight portal translation placeholders
Comment |
[ It would have been helpful and time saving to know, that there are a few manual steps to be done either during or in the aftermath of the upgrade:
* removal of the corrupted Insight file ($JIRA_HOME/plugins/installed-plugins/insight-9.1.13-QR-0023.jar) * empty cache (requires a restart) * add new Insight plugin to $JIRA_HOME/plugins/installed-plugins from Service Management package At least the steps above have helped us. Not sure if the second step with cache is really necessary though. ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
Support reference count | Original: 5 | New: 8 |
UIS | Original: 13 | New: 15 |
UIS | Original: 12 | New: 13 |
Support reference count | Original: 4 | New: 5 |
UIS | Original: 10 | New: 12 |
Support reference count | Original: 3 | New: 4 |
It would have been helpful and time saving to know, that there are a few manual steps to be done in the aftermath of the upgrade: