# Bug OP-6580 - Special characters (e.g. '#' and '&') trip up search autocompleter

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-6580

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 10.4.0 |
| Observed in versions |  |
| Sprint | 10.4.0 |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### **Steps to reproduce:**

1.  Enter a string into the search containing special characters (e.g.  '\#' and '&')

### **Actual Behavior**

Error message is displayed.

![](/api/v3/attachments/16918/content)

The string seems to be cut at the special character.

### **Expected Behavior**

The characters should be included in the search or, if that is not possible, they should be ignored.

### Notes

If one presses enter before the autocompleter is done, the search is triggered successfully.