That bug is pretty annoying for me as I try to improve our communication in work packages by more often using the double hash notation so that people can directly read the subject of a linked work package.

### Steps to reproduce

* In a rich text field like a work package description try to write "##<some WP id>", e.g. "##1234" Begin of the insertion


End of the insertion Begin of the deletion

End of the deletion ### What is the buggy behavior?

In contrast to the single hash notation:

* No auto-completer for selecting the work package is showing up, leaving me clueless if I referenced the correct work package. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * In the edit mode of a rich text field a double hash ID is not highlighted red, which would indicate that the linking was successful Begin of the insertion


End of the insertion Begin of the deletion

End of the deletion ### What is the expected behavior?

1. Auto-completer opens also for double and tripple hash notations Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion 2. The created link gets highlighted Begin of the insertion,End of the insertion Begin of the deletion red,End of the deletion just like when selected via single hash notation. Begin of the insertion


End of the insertion Begin of the deletion

End of the deletion Note that funnily saving the double hash notation still renders correctly at the moment.

### <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/53033/content">