Notification and issue security schemes cause import errors with PC 3.0

When importing notification schemes, the simulated import gives an error about not being able to create the notification scheme as it says that a notification scheme with a different name already exists but this does not happen when running the actual import. The message shows that the scheme is being created with the wrong name (actually the name of a different scheme). This will only happen if the import includes several notification schemes, but not in all cases.

The same would happen with issue security schemes.