External System Import updating Moved Issues via previous Issue Keys

Issue Summary

The process of importing data using External System Import can inadvertently lead to silent updates when issues have been moved across projects. If the issue key from the imported CSV file corresponds to an issue that was previously moved to a different project, the system performs an automatic update on the relocated issue. This unanticipated update, in some cases, results in data loss.

By implementing a user-controlled warning screen, the system can prevent unintentional updates to moved issues, offering users the opportunity to manage and decide the fate of these associations during the import process.

Steps to Reproduce

1. Create a Project A (PA) and Project B (PB).
2. Create issues within PA (e.g., PA-1, PA-2, PA-3).
3. Move issues from PA to PB (e.g., PA-1 moved as PB-1).
4. Permanently delete PA project.
5. Re-create PA project (using the same Project Key), and import PA-1 issue along with other data using the External System Import feature.
6. Automatic update of PB-1, leading to data overwriting.

Expected Results

Proposing the introduction of a warning mechanism in the form of a screen prompt. When the system encounters issue keys associated with previously moved issues, this screen would intercept the automatic redirection and update process. Instead, it would present users with the choice to proceed or abort the update to the associated issue. This proactive approach aims to empower users with awareness and control over such associations, thereby reducing inadvertent actions and fostering a more user-centric experience.

Actual Results

Issues that were previously moved undergo automatic updates, resulting in potential data loss in certain scenarios.