Skip to content

Move vulnerability creation out of transaction

What does this MR do and why?

This MR moves vulnerability creation out of the issue link transaction. With the creation code in the transaction, it creates a subtransaction when it hits Vulnerabilities::CreateService, as described in #386323 (closed). Creating an issue then failing the issue creation is not a problem, as it creates one not on the default branch which will either be promoted with the merge or handled if not merged.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #386323 (closed)

Merge request reports