Migration status label 'Failed' doesn't listed after upgrading to CCMA 3.4.15 and 3.4.17

Issue Summary

When performed the migration with CCMA 3.4.13 in where same spaces failed to migrate. When selecting spaces for a new migration with CCMA 3.4.13, those spaces are correctly marked as failed in UI.
After updating to CCMA 3.4.15 and 3.4.17, users are not being able to select failed spaces based on the migration status - those failed spaces are incorrectly listed as migrated.
Now, if you go back to CCMA 3.4.13, those spaces are correctly labelled again as failed.

The attached screenshot depicts the problem.  

Steps to Reproduce

1. Migrate a few spaces in CCMA 3.4.13
2. You may see a few spaces in Failed status for various reasons
3. Users would be now able to select those failed spaces based on migration status in 3.4.13 in their new Migration plan 
4. Update your CCMA version to 3.4.15 or 3.4.17
5. users are not being able to select those failed spaces based on the migration status instead it shows those failed spaces are incorrectly listed as Migrated.

Expected Results

users should be able to select spaces based on the migration status i.e. failed 

Actual Results

Instead, UI shows incorrect migration status for failed spaces in UI after updating to 3.4.15 or 3.4.17 

Workaround

None