Order of Jira Issues Keys
When you perform a Bulk Clone or Epic Clone, the work items are usually created in the order of the original issue keys.
For example, if you are Bulk Cloning WORK ITEM-1, WORK ITEM-2, and WORK ITEM-3 we typically create the cloned work items in this order.
If the source space (project) contains Epics and the Link to cloned epic (if available) option is selected, Deep Clone will prioritize the Epics, and clone the Stories right after the Epic, which will change the key ordering.
Subtasks are created right after their parents, e.g., if WORK ITEM-1 has the subtask WORK ITEM-25, they will be cloned as CLONE-1 and CLONE-2.
Work items may have been deleted in the source space (project). For example, if WORK ITEM-2 has been deleted, WORK ITEM-1 and WORK ITEM-3 will be cloned as CLONE-1 and CLONE-2.
Known Limitation
We cannot influence the numbering of the issue keys. When Deep Clone creates a work item in your instance, the issue key is generated just as if a Jira user creates a work item manually. This means if the last work item that was created in the target space (project) had the issue key WORK ITEM-300, the issue key of the following work item will be WORK ITEM-301.
