OTRS import fails when default closed states at the OTRS side not exist

[dominikklein]

Used Zammad Version

6.2.x (develop)

Environment

• Installation method: any
• Operating system (if you're unsure: cat /etc/os-release ): any
• Database + version: any
• Elasticsearch version: any
• Browser + version: any

Actual behaviour

Currently, the OTRS import fails when default closed states at the OTRS side do not exist.

https://community.zammad.org/t/errors-encountered-during-otrs-to-zammad-migration/12449/6

Expected behaviour

The import should work, also when only other closed states at the OTRS side exist.
But at least one closed state needs to exist on the OTRS side, otherwise, it seems to be a broken OTRS setup, which leads also to an not working Zammad import and system.

Steps to reproduce the behaviour

• Delete default closed states and create a different closed state inside OTRS.
• Try to use the import on the Zammad side.

Support Ticket

No response

I'm sure this is a bug and no feature request or a general question.

yes