**As** an administrator who wants to switch from regular numeric identifiers to semantic identifiers
**I want to** have job running in the background which does the migration for me

**Acceptance criteria**

* There is a background job for generating project based semantic work package Begin of the insertionIDsEnd of the insertion Begin of the deletion idsEnd of the deletion

* 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 Begin of the insertionIDsEnd of the insertion Begin of the deletion idsEnd of the deletion is set

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


**Technical notes**

* We need a separate table to connect project based sequence numbers with actual work packages (columns Begin of the insertion`project_id`, `sequence_number`, `work_package_id`)End of the insertion Begin of the deletion project\_id, sequence\_number, work\_package\_id)End of the deletion

* 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 Begin of the insertionJiraEnd of the insertion Begin of the deletion jiraEnd of the deletion migration team can start using them as well Begin of the deletion


**Permissions and visibility considerations**

* _To whom is this feature visible?_

* _When is it not visible?_


**Translation considerations**

* _Key terms and phrases in the key languages_End of the deletion


**Out of scope**

* <br>


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