Issue Summary

Imported Jira Cloud software work items were left orphaned without a visible project key prefix (e.g., "-1234" instead of "ABCD-1234") after a CSV import. This occurred when a project was deleted and its key was immediately reused for a new import while the original project was still in the recycle bin/trash. These orphaned items cannot be opened or edited and redirect to an error page.

Steps to Reproduce

1. Create a Jira project with several work items.

1. Delete the project (it moves to the trash/recycle bin).

1. While the project is still in the trash, perform a CSV import using the old Import Experience (JIM), attempting to use the same project key as the deleted project.

1. Observe that work items are created without the project key prefix 

Expected Results

The CSV import should either fail if the key is reserved/in-use in the trash, or it should correctly associate the new work items with the new project and assign the proper project key prefix.

Actual Results

Work items are created as orphaned entities. In the database, they are stored with a purely numeric entityKey (e.g., 1234) instead of the standard PROJECT-KEY format. Searching for these items returns results like "-1234" which, when clicked, redirect to an error page or the public Jira portal.

Workaround

You may reimport the Jira work items using csv import into a different project & delete the Blank Project/Space which in turn will delete all the orphaned Jira work items