<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=592545) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Since upgrading our GitLab instance to 18.9, Embedded Views (GLQL) in Merge Requests fail to render, returning an HTTP 500 Internal Server Error. ### Steps to reproduce 1. Upgrade GitLab instance to version 18.9. 2. Create or open a Merge Request in a project (e.g., foo/codebase). 3. Add an embedded GLQL view in the MR description with a query referencing a different project path, for example: ``` query: type = issue AND project = "bar/project" AND id in ( 1, 2 ) title: Gitlab ticket this MR resolves description: Related ticket(s) will be resolved on merge. display: list collapsed: true limit: 5 fields: title, description, state, milestone ``` 4. Observe that the embedded view fails to render. Note: Even simplifying the query to type = issue (without a cross-project reference) does not render the codebase's own issues. ### What is the current *bug* behavior? Instead of rendering the embedded view, an error infobox is displayed: {width=900 height=91} The network request to the GLQL API returns HTTP 500 with: ```[{"message": "Internal server error"}]``` The API call appears to use the MR's project path rather than the queried project path: ```https://GITLAB_INSTANCE/api/glql?project=foo%2Fcodebase``` ### What is the expected *correct* behavior? The embedded GLQL view should render correctly in the Merge Request, displaying the queried issues as a list, as it did prior to the 18.9 upgrade. <!-- If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"` -->