Content
View differences
Updated by Rosanna Sibora 8 days ago
The auto-incrementing sequence number which is part of every work package key is dependent on the project and type. For every project and type combination it starts with 1.
* Projects have a short name, e.g. `oD` for openDesk (1 to 10\* 8 chars).
* Types have a short name, e.g. `CR` for Change Request (1 to 8 chars).
**Implementation steps**
1. Step 1: {projectkey}-{sequence} (Jira case)
1. `oD-2212`
2. `HR-123`
2. Step 2: custom pattern
1. `oD_CR-1`
2. `oD_D-4`
3. `oD_EPIC-35`
4. `oD_BUG-223`
**More requirements:**
* When creating a new project, I can specify a custom project key (e.g., "MKTG" for Marketing, "DEVOPS" for DevOps).
* The system validates that the project key is unique across all projects.
* If no custom key is provided, the system auto-generates one from the project name, based on the rules below.
* 3 first characters from project name (e.g., "Marketing Team" → "MAR").
* In case this key is already taken, use 4 or more characters.
* Changing type or moving the work package to another project updates the key.
* Historical references and links remain functional after key changes.
* Administrators can edit an existing project's key through project settings.
* When changing a project key, the system displays a warning about the impact on existing work packages.
* All existing work package identifiers automatically update to use the new key (e.g., OLD-123 becomes NEW-123).
* The system performs a background re-index after key changes.
* Historical references and links remain functional after key changes.
* The numeric sequence continues incrementally regardless of key changes.
* A key can not be used twice. It is blocked also after deleting the work package, moving project or changing type.
**Requirements to allow Jira migrations (Step 1):**
* Allow handling of project key size of \*2-255 characters.
* Allow usage of any characters from A to Z, digits from 0 to 9 and the underscore character.
* Projects have a short name, e.g. `oD` for openDesk (1 to 10\*
* Types have a short name, e.g. `CR` for Change Request (1 to 8 chars).
**Implementation steps**
1. Step 1: {projectkey}-{sequence} (Jira case)
1. `oD-2212`
2. `HR-123`
2. Step 2: custom pattern
1. `oD_CR-1`
2. `oD_D-4`
3. `oD_EPIC-35`
4. `oD_BUG-223`
**More requirements:**
* When creating a new project, I can specify a custom project key (e.g., "MKTG" for Marketing, "DEVOPS" for DevOps).
* The system validates that the project key is unique across all projects.
* If no custom key is provided, the system auto-generates one from the project name, based on the rules below.
* 3 first characters from project name (e.g., "Marketing Team" → "MAR").
* In case this key is already taken, use 4 or more characters.
* Changing type or moving the work package to another project updates the key.
* Administrators can edit an existing project's key through project settings.
* When changing a project key, the system displays a warning about the impact on existing work packages.
* All existing work package identifiers automatically update to use the new key (e.g., OLD-123 becomes NEW-123).
* The system performs a background re-index after key changes.
* Historical references and links remain functional after key changes.
* The numeric sequence continues incrementally regardless of key changes.
* A key can not be used twice. It is blocked also after deleting the work package, moving project or changing type.
**Requirements to allow Jira migrations (Step 1):**
* Allow handling of project key size of \*2-255 characters.
* Allow usage of any characters from A to Z, digits from 0 to 9 and the underscore character.