-
Bug
-
Resolution: Fixed
-
Low
-
5.16.0, 5.15.2, 5.16.1, 5.17.2
-
2
-
Severity 3 - Minor
-
4
-
Issue Summary
Unable to update other object type mapping configurations if the Match Identified option is set to Case insensitive
This is reproducible on Data Center: yes
Steps to Reproduce
- Find an existing object type mapping (import configuration) with the Match Identifier already set to Case insensitive.
- Edit the mapping, change some other settings like the Missing objects from Ignore to Remove or vice versa.
Expected Results
Update is successful without any error on the UI or in the log
Actual Results
- On the mapping screen, the Match Identifier is automatically switched to Case sensitive without any action on this field.
- Update fails with 'Something went wrong. Contact Administrator'.
- The below exception is thrown in the atlassian-jira.log file:
2024-08-09 14:15:55,005+0000 http-nio-8080-exec-19 url: /jsm/rest/insight/1.0/importsource/ot/; user: admin ERROR admin 855x257x1 1rf7q63 172.29.208.218,172.50.0.2 /rest/insight/1.0/importsource/ot/ [c.r.j.p.i.c.w.a.r.exception.mapper.DefaultMapper] Unexpected exception was thrown while processing the request com.fasterxml.jackson.databind.exc.InvalidFormatException: Cannot deserialize value of type `boolean` from String "falseselected": only "true"/"True"/"TRUE" or "false"/"False"/"FALSE" recognized at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 1199] (through reference chain: com.riadalabs.jira.plugins.insight.channel.web.api.rest.model.imports.configuration.ImportSourceOTEntry["matchIdentifierIgnoreCase"]) ...
Workaround
Re-create the object type mapping with the desired options as editing after creation is not possible due to JSDSERVER-15396 Not able to change MatchIdentifier option in Import objecttype mappings.
- is caused by
-
JSDSERVER-15396 Not able to change MatchIdentifier option in Import objecttype mappings
-
- Closed
-