Issue Summary

This is reproducible on Data Center: (yes) 

In this scenario, migrating a project containing a Sprint with a name that already exists in the cloud results in that existing Sprint being modified instead of a new Sprint being created.

Steps to Reproduce

1. In server, create a new project:

• Name: Sprint Test 1
• Key:  SPRINT1

2. Create a test issue: SPRINT2-1

3. Create a sprint: SPRINT1 Sprint 1

4. Add the test issue to sprint.

5. Migrate SPRINT1 project to cloud.

6. Execute this SQL query against the cloud database to see the migrated Sprint:

select "ID", "CLOSED" from "AO_60DB71_SPRINT" where "NAME" = 'SPRINT1 Sprint 1'

Example results:

7. In server, find that project that was just migrated and change the name and key:

• New Name: Sprint Test 2
• New Key: SPRINT2

8.  Find the Sprint 'Sprint1 Sprint 1' and complete the Sprint.

9. Migrate the SPRINT2 project to the cloud.

Expected Results

The cloud site will now have two results for this query:

select "ID", "CLOSED" from "AO_60DB71_SPRINT" where "NAME" = 'SPRINT1 Sprint 1'

Actual Results

The existing Sprint from the cloud with the same name is updated.  The results of that SQL query now look like this:

The Sprint associated with the existing project in the cloud has been modified by the migration of the new project.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available