<!--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=439700) </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 When a pipeline triggers downstream pipelines, the security MR Widget does not show if the security scanners do not run in the main pipeline but **only** in the child pipelines. ### Steps to reproduce Create a pipeline that does nothing else than trigger a child pipeline. In this child pipeline, run the SAST template. ### Example Project https://gitlab.com/gl-demo-ultimate-odupre/public/iac-terraform-multi-environments/-/merge_requests/3 ### What is the current *bug* behavior? The MR widgets do not show. ### What is the expected *correct* behavior? The MR widgets should show no matter where the security (or performance, or quality) reports are produced. ### Output of checks <!-- If you are reporting a bug on GitLab.com, uncomment below --> This bug happens on GitLab.com cc @minac FYI: https://gitlab.slack.com/archives/C8S0HHM44/p1706540311487409?thread_ts=1704295381.953209&cid=C8S0HHM44