Issue Summary

Users are not able to update the 'MatchIdentifier' configuration from 'Case insensitive' to 'Case sensitive' in import object type mappings. It fails with the error - "Something went wrong. Contact Administrator'.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create a import configuration. 
2. Add the object type mapping for any object type and save it. 
3. We can see the 'Match Identifier' is by default set to 'Case Sensitive'.
4. Open the configuration again, and change it to 'Case InSensitive' and save it. 
5. Now, open the configuration again and change it to 'Case Sensitive'.

Expected Results

The identifier changes without any error.

Actual Results

The operation fails with 'Something went wrong. Contact Administrator'.

The below exception is thrown in the atlassian-jira.log file:

2024-06-19 20:35:07,622+0530 http-nio-45161-exec-2 url: /j5161/rest/insight/1.0/importsource/ot/; user: admin ERROR admin 1235x464x1 153c4im 0:0:0:0:0:0:0:1 /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 "trueselected": only "true"/"True"/"TRUE" or "false"/"False"/"FALSE" recognized
 at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 1052] (through reference chain: com.riadalabs.jira.plugins.insight.channel.web.api.rest.model.imports.configuration.ImportSourceOTEntry["matchIdentifierIgnoreCase"])
        at com.fasterxml.jackson.databind.exc.InvalidFormatException.from(InvalidFormatException.java:67)
        at com.fasterxml.jackson.databind.DeserializationContext.weirdStringException(DeserializationContext.java:1958)
        at com.fasterxml.jackson.databind.DeserializationContext.handleWeirdStringValue(DeserializationContext.java:1245)
 

Workaround

At this point, the only workaround is to take a screenshot of the attribute mappings, delete the import mapping for the problematic object type, and then create a new one with similar mappings.  As the newly created mapping configuration comes with 'Case sensitive' option, this will help you to overcome this issue.