# Feature COMMS-711 - Adapt work package link blocks in BlockNote for project-based semantic work package identifiers

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| 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

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Documents |
| 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 | Judith Roth |
| 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 document

**Acceptance criteria**

  - If the instance is set to project-based work package identifiers, the work package link block inside documents
    
      - shows the project-based semantic work package identifier instead of the numeric ID.
    
      - 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 showing 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**

  - Some translations included the "\#" for the classic ID. That was removed and the other languages need to be adapted accordingly.

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