# Feature COMMS-628 - Administration setting for project-based work package identifiers

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.5.0 |
| Sprint | BlockNote Update; Finishing Identifiers; Starting Versions |
| 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-653 | Administration setting for sematic work package identifiers UI | Implementation | closed |  | 17.4.0 |  |
| COMMS-654 | Ensure project identifiers are persistent URIs | Implementation | rejected |  | 17.3.0 |  |
| COMMS-669 | Update administration setting for sematic work package identifiers UI against project historical identifiers model | Implementation | closed |  | 17.4.0 |  |
| COMMS-672 | Support setting-aware project identifier casing with case-insensitive uniqueness | Implementation | closed |  | 17.4.0 |  |
| COMMS-682 | Rename work packages identifier settings to semantic | Implementation | closed |  | 17.4.0 |  |
| COMMS-734 | Refine wording for work package identifier settings | Implementation | rejected |  |  |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| COMMS-673 | Task | Consider increasing the suffix limit from 10,000 to cover non-latin languages | rejected | Kabiru Mwenja | 17.4.0 |  |  |
| COMMS-740 | Bug | Admin page for semantic IDs: grammatical issue | closed |  | 17.5.0 |  | Administration |
| COMMS-793 | Bug | Inconsistent naming on admin page | closed |  | 17.5.0 |  |  |
| COMMS-742 | Bug | Admin page for semantic IDs: long ids cause overflow | closed |  | 17.5.0 |  | Administration |
| COMMS-737 | Bug | After migration job is complete save button is visible and clicking it triggers a 404 | closed |  | 17.5.0 |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Administration, Modules and project features / Work packages, Modules and project features / Project settings |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/NHUuezDJWmeG8LsH2OgVMh/Project-identifiers?node-id=25-10420&t=1Fh63upnBJSZUOL8-4 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | Kabiru Mwenja |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** an admin  
**I want to** have a setting where I can decide between regular numeric work package IDs and project-based semantic work package IDs  
**so that** I can enable semantic work package IDs

**Acceptance criteria**

  - In "Administration" -\> "Work Packages" is a new sub menu item "Identifier"

  - For now, this is only accessible with a feature flag `SEMANTIC_WORK_PACKAGE_IDS`

  - In the new administration page, it should be possible to choose between
    
      - Instance-wide numerical sequence (default)
    
      - Project-based alphanumerical identifiers

  - See mockup for exact wording and help texts

  - When selecting Project-based alphanumerical identifiers
    
      - If there are existing project identifiers which are more than 10 characters or contain a dash, we will show a table with
        
          - Name
        
          - Current identifier
        
          - Automatically generated suggestion for a shorter identifier
    
      - The table has 5 entries to begin with and a "show more" to show the rest if there are more than 5
    
      - The table only contains entries for problematic project identifiers (too long or containing a dash)
    
      - There is a button to accept all changes and activate the new setting

  - After the user clicks to accept we start a background job to generate the new identifiers (<mention class="mention" data-id="71645" data-type="work_package" data-text="#71645">\#71645</mention>) and show a progress bar.
    
      - While the job is running, it should not be possible to change the setting.
    
      - When the user closes the page and navigates back to it while the job is running, the progress bar is shown and the setting can not be changed.
    
      - When the background job is finished, the page reloads, the new setting is set to project-based identifiers and can be edited again
    
      - It is NOT possible to abort the background job. ~~When it is aborted, the page reloads and the setting is set to global numeric identifiers and can be edited again~~

**Technical notes**

  - When selecting global numeric identifiers (after project-based identifiers were active before), the already existing semantic identifiers are not deleted (so that we can still resolve URLs with semantic identifiers)

  - We need an algorithm / class to generate short project identifiers. This should be written in a way so it can be reused and applied when a new project is created.

**Permissions and visibility considerations**

  - This is visible to everyone who is allowed to access and change global settings

**Translation considerations**

  - Key terms are
    
      - Instance-wide numerical sequence
    
      - Project-based alphanumerical identifiers

**Out of scope**

  - Implementation of the background job to generate the new identifiers  (see <mention class="mention" data-id="71645" data-type="work_package" data-text="#71645">\#71645</mention>)

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*
