# Feature COMMS-712 - Adapt work package links in CKEditor for project-based semantic work package identifiers

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.5.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| COMMS-728 | Use formatted_id and displayId for #123 work package text macros | Implementation | rejected |  | 17.5.0 |  |
| COMMS-771 | Use formatted_id in user-facing WP identifier rendering | Implementation | closed |  | 17.5.0 |  |
| COMMS-772 | Share semantic-id predicates and pin the route constraint | Implementation | closed |  | 17.5.0 |  |
| COMMS-773 | Resolve semantic identifiers in wiki reverse-link parser | Implementation | closed |  | 17.5.0 |  |
| COMMS-774 | Accept semantic work-package identifiers in text macros | Implementation | closed |  | 17.5.0 |  |
| COMMS-775 | Editor round-trip — semantic-id-aware mention contract | Implementation | closed |  | 17.5.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| COMMS-786 | Bug | Numeric ID visible in edit mode in links with #  | closed |  | 17.5.0 |  | Modules and project features / Work packages, Modules and project features / Text editor / CKEditor5 |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | Kabiru Mwenja |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**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
    
      - 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>

**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.*
