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

      1. Install JSM 4.20.14
      2. Set up an Insight object field on case creation, visible from the portal (single or multiple, it doesn't matter)
      3. 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:

      1. "Search for an object"
      2. "Search for objects"

      Actual Results

      The placeholders' key is displayed instead:

      1. rlabs.insight.i18n.plugin.configure.portal.single.default
      2. rlabs.insight.i18n.plugin.configure.portal.multiple.default

      See for instance:

      Workaround

      1. Find and unzip the insight jar file (insight-9.1.13-QR-0023_1666247918000.jar)
      2. In the resulting folder, look for file properties/i18n.properties
      3. 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
      4. Repackage the archive (i.e. zip the files again, replace the extension with "jar")
      5. 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

            Johannes Rudolf added a comment - - edited

            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:

            • stop JIRA
            • delete defected Insight JAR file ($JIRA_HOME/plugins/installed-plugins/insight-9.1.13-QR-0023.jar)
            • empty cache
            • start JIRA

            Johannes Rudolf added a comment - - edited 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: stop JIRA delete defected Insight JAR file ($JIRA_HOME/plugins/installed-plugins/insight-9.1.13-QR-0023.jar) empty cache start JIRA

            I am waiting release

            Gonchik Tsymzhitov added a comment - I am waiting release

            aa39ef26d329 - I can see you were asking for a release inclusive of a fix. I can see the fix version for this issue was marked today as 8.20.16 I hope that helps!

            Stefano Capuzzimato (Inactive) added a comment - aa39ef26d329 - I can see you were asking for a release inclusive of a fix. I can see the fix version for this issue was marked today as 8.20.16 I hope that helps!

            Gonchik Tsymzhitov added a comment - - edited

            Hi awesome team,
            any plans to provide a new release ?
            And it will be good, it to see in 8.20.15

            Gonchik Tsymzhitov added a comment - - edited Hi awesome team, any plans to provide a new release ? And it will be good, it to see in 8.20.15

            Good to know, we're going to do the same however this workaround has to be applied after each update until this is fixed.

            Johannes Rudolf added a comment - Good to know, we're going to do the same however this workaround has to be applied after each update until this is fixed.

            I confirm the workaround fixes the issue on our end.

            One observation, on our end the file is named insight-9.1.13-QR-0023.jar instead of insight-9.1.13-QR-0023_1666247918000.jar as mentioned in the bug.

            Emanuel Jianu added a comment - I confirm the workaround fixes the issue on our end. One observation, on our end the file is named insight-9.1.13-QR-0023.jar instead of insight-9.1.13-QR-0023_1666247918000.jar as mentioned in the bug.

              4dcffb92068e Orest Busel (Inactive)
              scapuzzimato Stefano Capuzzimato (Inactive)
              Affected customers:
              5 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: