🎨 Design: Allow users to prioritise security approval as first things in MR which needs to be checked

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem

This is an insights from an research session.

Now currently, Security approval rules are not guided for devs to review first, it often happens that when user ask frontend, backend, qa to review the MR and then they realised that they can't merged it. They needs to fix the security issue first and the re-run the pipeline, but because of the code change, they need to ask frontend, backend and qa to redo it. It is an annoying experiences for devs.

Potential solution

Have an option security policy to allow user prfioritize security rules, if it turns on, on the MR page, we need to highlight security approval policy