[ihordubas99]

Ticket

https://community.openproject.org/wp/SE-641

What are you trying to accomplish?

Users can mention people in a document. Typing @ in the document editor opens a menu with the members of the document's project who are not locked, and the picked user is inserted as an inline mention with avatar and name. The mentioned user gets notified. The mention is stored in the document description as the same <mention> tag CKEditor writes, so it renders as a user link with a hover card wherever the description is shown.

The editor, the stored format and the notification call live in op-blocknote-extensions (#26018). The notification endpoint comes from #26028. This PR wires them into OpenProject.

Screenshots

What approach did you choose and why?

Notifications. Hocuspocus saves the changes of everyone editing with the token of the first user who connected, so the save can't tell who added a mention. The editor therefore notifies through POST /api/v3/notifications when a mention is inserted, with the session of the user who inserted it. For that it needs the document, so the document id now goes from the form through the block_note_editor input and component into a document-id attribute, and from there into initializeOpBlockNoteExtensions. The editor registers UserMentionNotificationExtension, which sends the request.

Menus. The document editor now renders the library's <OpenProjectMentionMenu /> and <OpenProjectHashMenu /> instead of wiring suggestion menus by hand. The hand-wired # menu had lost the library's rule that a fifth hash is not a command, and using the components keeps both menus in line with the library.

Stored format. The hocuspocus schema registers the server-side mention spec, so the stored markdown contains the canonical <mention> tag. A test pins the exact tag in the saved description.

This needs a release of @openproject/op-blocknote-extensions that contains mentions (#26018) and the notification endpoint (#26028). The dependency in frontend/package.json and extensions/op-blocknote-hocuspocus/package.json will be bumped before merging, so CI fails until then.

AI involvement

Collaborative – AI generated a substantial part of the code; I reviewed and understand every line.

Merge checklist

• Added/updated tests
• Added/updated documentation in Lookbook (patterns, previews, etc)
• Tested major browsers (Chrome, Firefox, Edge, ...)