# Feature COMMS-695 - Adapt work package lists for project-based semantic work package identifiers

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

## 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-705 | Use displayId in InfoLineComponent | Implementation | closed |  | 17.4.0 |  |
| COMMS-706 | Use formattedId in autocompleter and global search results  | Implementation | closed |  | 17.5.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| COMMS-713 | Bug | Lists of work packages should sort correctly by semantic id | closed |  | 17.5.0 |  |  |
| COMMS-719 | Code maintenance | cast displayId as string consistently | rejected | Kabiru Mwenja |  |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Work packages |
| 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 OpenProject instance which is set to use project-based work package identifiers  
**I want to** See project-based work package identifiers in the lists of work packages

**Acceptance criteria**

  - If the instance is set to project-based work package identifiers, the work package list shows the project-based work package identifier instead of the database ID in the ID column

  - The same is true for all other places where we show lists of work packages, e.g. the lists inside the work package show view (e.g. "Belongs to", "Previous Chunks", "Related to", "Subitems" etc.

  - If sorted by ID, Sorting should be done by project identifier and then by sequence, therefore: AA-1, AA-2, ... AA-10, BB-1, BB-2,... BB-10, ... (that's how Jira is sorting)

**Technical notes**

  - needs <mention class="mention" data-id="73715" data-type="work_package" data-text="##73715">\#\#73715</mention> to be decided first

  - depends on <mention class="mention" data-id="73735" data-type="work_package" data-text="###73735">\#\#\#73735</mention>

  - no truncation of the value should be necessary

**Out of scope**

  - Adapting search boxes (e.g. "Add new child" opens dropdown)

  - Adding additional columns (for now - if later on there is the need to have *both* the semantic ID and the database ID in a table, we can still add a database ID column that is only selectable when the instance is in semantic mode)
