Issue Summary

When trying to re-import a project with JCMA, active/future/closed sprints might drift from the original migration and cause issues such as this one:

2020-08-03 18:56:24.134 ERROR MOVE project-import We couldn't import Issue MOVE-2. Reason: Issue can be assigned to only closed sprints, and one active or future sprint during migration.. This caused 7 other items to fail.

Steps to Reproduce

1. Migrate a project with an active sprint and a future sprint using JCMA
2. Once migrated, delete the project (this is a common step done by customers who are done testing the migration of that project)
3. Note: the sprint data remains in Cloud after the project is deleted
4. Complete the Active sprint in Server
5. Add MOVE-2 to the future sprint in Server (e.g. edit the Sprint field)
    
   
6. Re-migrate the project
7. The migration will fail with 

   2020-08-03 18:56:24.134 ERROR MOVE project-import We couldn't import Issue MOVE-2. Reason: Issue can be assigned to only closed sprints, and one active or future sprint during migration.. This caused 7 other items to fail.

*This is just one of many scenarios that may lead to these drifts.

Expected Results

JCMA should re-migrate the entire project and its Sprint to issue associations

Actual Results

There are unhandled exceptions where JCMA thinks the following condition is not met, even though MOVE-2 is only assigned to a Closed and an Active sprint in Server.

"An issue can only be assigned to one active sprint or future sprint. This means you can't add an issue to both an active sprint and a future sprint at the same time."

Also notice that the same sprint is now shown as Active in Server and Future in Cloud, with the missing issue not present.

Server - Active

Cloud - Future

Workaround

NA