Setting "Delete" in the import configuration for handling missing objects is really dangerous and may delete all objects and all the connections to existing issues' custom fields. At least if you don't know 100% how it works.Take a look at this example (which luckily happened in our test environment): - We have an Insight structure with a lot of objects connected to about 50000 issues. - An import is run manually each week to update objects (which works fine with "Update" option selected) - Someone wants to add a few new objects by importing them. Thus he creates a new import configuration. As he is not aware of what the options mean, he leaves option to the default option "Delete". Threshold is by default set to 1 Day. - He runs the import once and his new objects are created and everything looks fine. - Two days later we realize that all objects except the new ones are deleted as the import as passed the threshold of 1 day. As the import is automatically set to autosync it has run every night since.The effect of this is that we would need to reimport all objects and the objects referring to the deleted ones, bulk change all issues to point to the new object keys. And not to mention all filters querying on the old object keys. Glad this was in test Proposed solution: # This problem would be avoided if "Ignore" was set as the default value as this will not destroy anything. An unexperienced user would probably think twice before changing to Delete. # Uncheck the "automatic synchronise" as this might result in passing the threshold without knowing. And as well - as all imports have the same default cron expression, it might hit hard on performance when lots of jobs start at the same time.Easy solution to implement which is needed - especially now that we will have many new unexperienced users in Insight.