Content
View differences
Updated by Wieland Lindenthal 3 months ago
**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._
**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._