-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Cloud to Cloud Migrations - Jira
-
None
-
1
-
Jira Software
Issue Summary
When a project is deleted in a sandbox environment and a user attempts to re-copy the same project from production using selective data copy, the preflight validation still reports "project already exists" — blocking the copy. The validation checks historical project keys rather than current state, preventing re-use of previously deleted project keys in the target sandbox.
Steps to Reproduce
- Copy a project from production to sandbox using selective data copy
- Delete the copied project in the sandbox environment (fully delete, not just trash)
- Attempt to copy the same project from production to sandbox again using selective data copy
- Run the preflight validation step
Expected Results
The validation should pass successfully and allow the selective copy to proceed, since the project no longer exists in the target sandbox.
Actual Results
N/A — No log file access available. The failure surfaces in the UI during the preflight validation step with a message indicating the project already exists in the target environment.
Workaround
- Change the project key on the source before running the copy — this bypasses the historical key check.
- Use a full data copy instead of selective — ⚠️ Warning: This will completely overwrite ALL existing data in your sandbox environment, including any configurations, issues, or test data. This action cannot be undone.
- blocks
-
CLOUD-11717 When doing a C2C migration, the preflight check "Project already exist" triggers for projects with different Key and Name
-
- Closed
-