**As** an administrator who wants to switch from regular numeric identifiers Begin of the insertionto project-based semanticEnd of the insertion Begin of the deletion to semanticEnd of the deletion identifiers
**I want to** have Begin of the insertionaEnd of the insertion Begin of the deletion job running in theEnd of the deletion background Begin of the insertionjobEnd of the insertion which does the migration for Begin of the insertionme.End of the insertion Begin of the deletion meEnd of the deletion

**Acceptance criteria**

* There Begin of the insertionareEnd of the insertion Begin of the deletion isEnd of the deletion a background Begin of the insertionjobsEnd of the insertion Begin of the deletion jobEnd of the deletion for

* applying changes to project identifiers and

* generating Begin of the insertionproject-basedEnd of the insertion Begin of the deletion project basedEnd of the deletion semantic work package IDs for all existing work packages

* When the job is aborted before it is finished and starts again, it can "pick up where it ended"

* At the successful end of the job the setting for semantic IDs is set

* When the user switches the setting for Begin of the insertionproject-basedEnd of the insertion semantic work package IDs Begin of the insertion onEnd of the insertion Begin of the deletion onEnd of the deletion and after a while off and after another while on again, the "old" semantic IDs should be "reused"


**Technical notes**

* Maybe this could be 2 jobs running after each other - one for setting the new project identifiers and one for setting the new Begin of the insertionproject-basedEnd of the insertion work package semantic ids?

* We need a separate table to connect project based sequence numbers with actual work packages (columns `project_id`, `sequence_number`, `work_package_id`)

* with uniqueness constraint

* We need a separate component which calculates the next available sequence number and tries to insert it - this can then be used in the migration job and on create or move of a work package

* It would be good to get at least the groundwork of new tables quite soon so the Jira migration team can start using them as well


**Out of scope**

* <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._