Content
View differences
Updated by Judith Roth 27 days ago
**As** a user of an instance set to use project-based semantic work package identifiers
**I want to** see project-based semantic work package identifiers when I link a work package inside a work package or meeting
**Acceptance criteria**
* If the instance is set to project-based work package identifiers, the work package link block inside CKEditor (e.g. work packages or meetings)
* shows the project-based semantic work package identifier instead of the numeric ID for the list of search results ID.
* shows the project-based semantic work package identifier instead of the numeric ID for the generated "link preview"
* uses the semantic ID in its link (? (? maybe we need to debate this)
* The semantic ID should be shown without an "#" sign, the database ID with an "#" sign
**Technical notes**
* Instead of the work package ID, the new field `display_id` (which was added to the API with <mention class="mention" data-id="73735" data-type="work_package" data-text="#73735">#73735</mention> ) needs to be used for the ID. It already considers the setting and the feature decision and therefore always shows the correct value (database ID or project-based semantic ID)
* The search itself does not need to be adapted, because this is already covered by <mention class="mention" data-id="73761" data-type="work_package" data-text="#73761">#73761</mention> data-text="#73761">#73761</mention>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Searching by project-based semantic work package identifiers is already covered by <mention class="mention" data-id="73761" data-type="work_package" data-text="#73761">#73761</mention>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** see project-based semantic work package identifiers when I link a work package inside a work package or meeting
**Acceptance criteria**
* If the instance is set to project-based work package identifiers, the work package link block inside CKEditor (e.g. work packages or meetings)
* shows the project-based semantic work package identifier instead of the numeric ID for the list of search results
* shows the project-based semantic work package identifier instead of the numeric ID for the generated "link preview"
* uses the semantic ID in its link (?
* The semantic ID should be shown without an "#" sign, the database ID with an "#" sign
**Technical notes**
* Instead of the work package ID, the new field `display_id` (which was added to the API with <mention class="mention" data-id="73735" data-type="work_package" data-text="#73735">#73735</mention> ) needs to be used for the ID. It already considers the setting and the feature decision and therefore always shows the correct value (database ID or project-based semantic ID)
* The search itself does not need to be adapted, because this is already covered by <mention class="mention" data-id="73761" data-type="work_package" data-text="#73761">#73761</mention>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Searching by project-based semantic work package identifiers is already covered by <mention class="mention" data-id="73761" data-type="work_package" data-text="#73761">#73761</mention>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._