Issue Summary

When changing a project's issue type scheme, Jira won't check if there are any archived issues that need to have their issue type changed. Then, when the archived issue is restored, it may keep an issue type that is no longer available in the scheme.

Steps to Reproduce

1. Create a new project on Jira
2. Create a new issue (Epic, for example)
3. Access the created Epic, then archive it
4. Navigate to the project's settings, then associate it with a new issue type scheme that doesn't contain the Epic issue type
5. Restore the Epic

Expected Results

Jira will ask users to migrate the issue type of the archived Epic in the project.

Actual Results

Jira allows the issue type scheme change and then keeps the affected issue type as Epic even after restoring it.

Workaround

Manually restore the issues in the affected issue type, then change the issue type scheme so they are correctly migrated to a valid issue type for the project.