Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-11950

Unable to synchronize and edit data locator of an object type mapping for a JSON import on upgraded JSM instance using Oracle as database

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 4.20.12
    • 4.20.8
    • Assets - Import

      Issue Summary

      After upgrading an JSM instance which is using Oracle as a database, it's not possible to update any data locators of an object type mapping of a JSON import, and synchronization is not possible. This affects all existing and new JSON import that has been configured.

      This is reproducible on Data Center: yes
      This is not reproducible on a vanilla instance, only on upgraded instance

      Steps to Reproduce

      1. Set up a JSM instance below version 4.15 with Oracle as the database.
      2. Set up Insight with a working JSON import.
      3. Ensure that you can edit the object type mapping to update any data locators.
      4. Upgrade the JSM instance to a recent version e.g. JSM 4.20.8.
      5. Edit the JSON import configuration to change any data locators.

      Expected Results

      The list of data locator will appear without any error on the screen

      Actual Results

      • The list of data locator will not appear
      • There's a pop-up error on the screen with text

        The Jira server was contacted but has returned an error response. We are unsure of the result of this operation.

      • After clicking on the OK button to dismiss the error dialogue, HTTP error code 500 can be seen in the browser's developer tools > Network tab. The response would look like the following.
        {"errorMessages":["Unable to get data locators for configuration of type {}ObjectTypeBean [id=1, name=JSON]"],"errors":{}}
        
      • Synchronization is not possible

      Workaround

      Update: This issue is not reproducible in JSM 4.0.12. It's recommended to upgrade to JSM 4.0.12 if the affected instance is on JSM 4.0.x or below.

      It's possible to update the data locator from directly from the database but with caution. The SQL query below can be used to retrieve the existing object type mapping configuration to be used for the update.

      select * from "AO_8542F1_IFJ_IMPORT_SRC_OTA" afiiso 
      where "IMPORT_SOURCE_OTID" in (
      	select "ID" from "AO_8542F1_IFJ_IMPORT_SRC_OT" afiiso 
      	where "IMPORT_SOURCE_ID" = (select "ID" from "AO_8542F1_IFJ_IMPORT_SRC" where "NAME" = 'name_of_the_JSON_import_configuration'))
      

            [JSDSERVER-11950] Unable to synchronize and edit data locator of an object type mapping for a JSON import on upgraded JSM instance using Oracle as database

            There are no comments yet on this issue.

              4dcffb92068e Orest Busel (Inactive)
              michin Michelle Chin
              Affected customers:
              14 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: