# Feature COMMS-699 - Search work packages by their identifier

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

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

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| COMMS-756 | Bug | Semantic ID is not shown in search results in different places | closed |  | 17.5.0 |  | Modules and project features / Work packages, Modules and project features / Search |
| COMMS-755 | Bug | Numeric ID in URL of the wp link when opened from search results | closed |  | 17.5.0 |  | Modules and project features / Work packages, Modules and project features / Search, Modules and project features / Query and filter |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Search |
| 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 |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a user who wants to find a work package by its project-based semantic identifier  
**I want to** get results on the global search  
**so that** I can easily find what I am searching for

**Acceptance criteria**

  - Searching for a project-based work package identifier in the global search finds the work package

  - Searching for a project-based work package identifier in the "ID" filter in the list of work packages finds the work package

  - Searching for a project-based work package identifier with the '\#' notation to link a work package inside another work packages description finds the work package

  - Searching for a project-based work package identifier when linking a work package inside a document finds the work package

**Technical notes**

  - 
    <br>

**Permissions and visibility considerations**

  - Visibility of work packages stays the same. Users should only find work packages they are allowed to access.

**Out of scope**

  - Other searches + filters (will be separate work packages)

  - Showing the semantic ID in the search results (those are separate work packages, e.g. <mention class="mention" data-id="74116" data-type="work_package" data-text="#74116">\#74116</mention> )
