Issue Summary

Users are experiencing issues with Markup and Link Search functionality in the Comments section of the Confluence Questions module. Specifically, while the comment field supports standard Confluence markup in edit mode, this markup is not correctly applied after saving.

Furthermore, the Link Search feature within comments or answers does not function as expected; although direct linking is possible, the search functionality fails to yield results.

Steps to Reproduce

1. Navigate to the Confluence Questions module and select any existing question or create a new one.
2. Scroll down to the 'Add a comment' section and enter any comment with standard Confluence markup (e.g., bolding text, adding bullets). Use the Link Search functionality to try to add a link by searching for a Confluence page instead of pasting the direct URL.
3. Save the comment.
4. View the comment to verify if the markup is applied as expected and if the link added via the Link Search is functioning properly.

Expected Results

• The comment should display with the applied markup correctly rendering as per Confluence's standard (e.g., text in bold, bullets displayed correctly).
• The Link Search feature should allow users to search for and insert links to other Confluence pages or external sites seamlessly, with search results being populated based on the input keywords.

Actual Results

After saving, the comment does not display the markup as it was entered in edit mode. Instead, the text appears without any formatting, ignoring the markup entirely.

When attempting to use the Link Search functionality within comments or answers, the search does not operate. No search results are shown, and users are unable to link to other Confluence pages or external sites through the search functionality, though direct linking (pasting the URL) still works.

This issue negatively impacts user experience by reducing the usability of comments for collaboration and information sharing within the Confluence Questions module.

 h3. Workaround
Currently, there's no workaround.