<!--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=512859) </details> <!--IssueSummary end--> ### Problem to solve <!-- What is the user problem you are trying to solve with this issue? --> As of recently direct-transfer migrates Vulnerability reports, which is great! However, it does not migrate their `statuses`. Meaning, when one migrates their project they have to update on destination all the findings that have been `resolved`, `dismissed` or `confirmed` on source. All the findings import with the default `detected` status ("Needs triage"). e.g. see the second screenshot below: | source | destination | |-|-| ||| **NOTE:** The # of vulnerabilities is also off (failed to import), but that is part of another issue: https://gitlab.com/gitlab-org/gitlab/-/issues/509904 ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> Migrate Vulnerability report `statuses` as part of a direct-transfer project bulk-import.