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

The modules rlabs-import-type should have standard properties across all modules.

    • 1
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Issue Summary:

      While working through a Groovy script to automatically disable/enable auto-synchronization, I came across what appears to be a bug or opportunity for improvement/standardization.

      When pulling the configuration of an ImportSource using the ImportSourceConfigurationFacade, and then importSource.getJsonConfiguration(), followed by setJsonConfiguration(), and ImportSourceConfigurationFacade.storeImportSource(), I found that certain import modules have differing property names for basic properties such as "userName".

      For example, the import module type of rlabs-import-type-csv and rlabs-import-type-json uses camel case "userName" for the username property.

      However, rlabs-import-type-database and rlabs-import-type-jira-environment modules use "username" (all lowercase).

      This is awkward when scripting because you have to actively check for which version of the username is being used, otherwise, errors are thrown, and the script fails.

      There may be other anomalies, but these are the ones I noticed. I'd like to request for the properties to be normalized/standardized across all import modules.

      This is confirmed in JSM 5.12.11

            [JSDSERVER-15533] The modules rlabs-import-type should have standard properties across all modules.

              Unassigned Unassigned
              c2a2d7e43832 Dan C
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: