# Feature COMMS-629 - Background job for converting project-based semantic work package identifiers

Project: Stream Communicator
Status: closed
URL: https://community.openproject.org/work_packages/COMMS-629

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.5.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| COMMS-664 | Batch convert existing project identifiers | Implementation | rejected |  | 17.4.0 |  |
| COMMS-665 | Batch add new semantic work package identifiers | Implementation | rejected |  | 17.4.0 |  |
| COMMS-666 | Create job shell for batch converting | Implementation | rejected |  | 17.4.0 |  |
| COMMS-758 | Make sure identifier conversions does cleanup upon failure | Implementation | closed | Tom Hykel | 17.5.0 |  |
| COMMS-759 | Add better progress indicator to identifier conversion page | Feature | closed |  | 17.5.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| COMMS-785 | Bug | Conversion stuck and not resumable for users after validation error during conversion job | closed |  | 17.5.0 |  |  |
| COMMS-714 | Bug | Automatically converting project identifiers should not lead to usage of reserved keywords | closed |  | 17.5.0 |  |  |
| COMMS-761 | Bug | Identifier conversion doesn't finish at the first attempt | closed |  | 17.5.0 |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | Tom Hykel |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an administrator who wants to switch from regular numeric identifiers to&nbsp;project-based semantic identifiers  
**I want to** have a background job which does the migration for me.

**Acceptance criteria**

*   There are background jobs for
    
    *   applying changes to project identifiers and
        
    *   generating project-based semantic work package IDs for all existing work packages
        
*   When the job is aborted before it is finished and starts again, it can &quot;pick up where it ended&quot;
    
*   At the successful end of the job the setting for semantic IDs is set
    
*   When the user switches the setting for project-based semantic work package IDs  on and after a while off and after another while on again, the &quot;old&quot; semantic IDs should be &quot;reused&quot;
    

**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 project-based 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._
