# Bug COMMS-714 - Automatically converting project identifiers should not lead to usage of reserved keywords

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Module |  |
| Target versions | 17.5.0 |
| Observed in versions |  |
| Sprint |  |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Use an instance with uses classic global database-based work package identifiers

2.  Create a project whose name will be converted to a shorthand that resembles a reserved keyword (e.g. new, menu):  
    \- new experimental wallet  
    \- My experimental new usage

3.  switch the instance to project-based semantic work package identifiers

4.  See the collisions (projects getting identifiers "NEW" and "MENU"

### What is the buggy behavior?

We don't want collisions with reserved keywords, even if they are downcased. We want all validations on the identifier to be honored.

### What is the expected behavior?

Other identifiers are chosen that don't collide with reserved keywords

### Background

<https://github.com/opf/openproject/pull/22765#discussion\_r3111337112>
