# Feature BNE-131 - Give feedback when waiting for work package search

Project: Stream BlockNote extensions
Status: closed
URL: https://community.openproject.org/work_packages/BNE-131

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.8.0 |
| Sprint | Sprint 11: Versions stabilization |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_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 / Text editor / BlockNoteJS / OpenProject Extensions |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| 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 insert a work package link in a document  
**I want to** get feedback while we are waiting for the network or when no results are found  
**so that** I don&#x27;t have to guess if it is still searching or not

**Acceptance criteria**

*   When searching for a work package a spinner is shown until the results are there
    
    *   When searching via slash command: Spinner appears at the right end of the input field
        
    *   When searching via hash: Spinner appears at the right end of the &quot;Type to search work packages&quot; message box
        
*   When no results are found, we show &quot;No results&quot; (inside or instead of the search result dropdown - not selectable of course)
    
*   When there is a network error we show &quot;Error. Unable to load content.&quot; (inside or instead of the search result dropdown - not selectable of course)
    

**Technical notes**

*   If possible, we should use the same spinner as Primer does (and we should use the same spinner everywhere where we need one - if necessary, align other places)
    

**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_&nbsp;
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
