During a complete project import, setting of version order within projects will always fail

During a complete project import, PC will automatically split the configuration import into two stages. The first stage will (also automatically) skip import of versions and components to make the project compatible with Jira builtin data import. However, the order of versions is managed as a property of the project (which is not skipped) so that will fail in the first stage of configuration import, as versions do not exist yet. The user will see an error like the one in the attached screenshot.

This fake error will confuse users but, even worse, the version order will never be set correctly, as project properties are skipped during the second import.