Content
View differences
**As** a system operator
**I want to** delete old versions of semantic project identifiers, which are still resolved by the system after rename operations
**so that** I may use the name for new or existing project.
**Acceptance criteria**
* `/admin/settings/project_reserved_identifiers` now shows up in is updated support semantic mode
* It lists every historical project identifier across both classic and mode, listing only reserved semantic modes -- even those that were active in first mode when it got converted to second mode
* Unreleasing an identifier breaks all previous URLs that used it, including the semantic work package links
* example:
1. OLDPROJ (with WP OLDPROJ-1) gets renamed to NEWPROJ (with WP NEWPROJ-1)
2. Links containing OLDPROJ or OLDPROJ-1 resolve correctly
3. The OLDPROJ identifier is released
4. Links containing OLDPROJ or OLDPROJ-1 get a 404
* Also, the term "release" is replaced with "unreserve" identifiers
**Technical notes**
* We need to:
* Delete that old slug from the `FriendlyId` table
* Delete all relevant entries from the `WorkPackageAlias` table
**I want to** delete old versions of semantic project identifiers, which are still resolved by the system after rename operations
**so that** I may use the name for new or existing project.
**Acceptance criteria**
* `/admin/settings/project_reserved_identifiers` now shows up in
* It lists every historical project identifier across both classic and
* Unreleasing an identifier breaks all previous URLs that used it, including the semantic work package links
* example:
1. OLDPROJ (with WP OLDPROJ-1) gets renamed to NEWPROJ (with WP NEWPROJ-1)
2. Links containing OLDPROJ or OLDPROJ-1 resolve correctly
3. The OLDPROJ identifier is released
4. Links containing OLDPROJ or OLDPROJ-1 get a 404
* Also, the term "release" is replaced with "unreserve"
**Technical notes**
* We need to:
* Delete that old slug from the `FriendlyId` table
* Delete all relevant entries from the `WorkPackageAlias` table