Consider bypassing the MR for setting up Secure features
Recommendation based on the UX scorecard:
For users that are familiar with Git and GitLab, setting up Secure features through an MR makes sense. But to users who aren't it's most likely very confusing. The experience feels disjointed and it's almost impossible for them to know what to do and when (for example, they need to wait for the pipeline to run to get the first results). They possibly don't even know what an MR is. That alone could cause enough confusion for them to abandon the process completely.
Could the Secure features be set up without a MR? We should explore designing an experience that works for everyone, including users who aren't familiar with Git and GitLab.
Edited by Matej Latin