-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
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
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-15533] The modules rlabs-import-type should have standard properties across all modules.
| Support reference count | New: 1 |
| Labels | New: ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 978833 ] |
| Description |
Original:
h3. 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 username is being used, otherwise errors are thrown, and the script fails. There may be other anomalies, but these are the ones I noticed, and I'd like to request a bug ticket to be made for the properties to be normalized/standardized across all import modules. |
New:
h3. 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 |
| Reporter | Original: Hugo Fernandes [ 7e87200788f9 ] | New: Dan C [ c2a2d7e43832 ] |