Flags deep dive: PR merge has workflow defects

When to use this Flag?

Leverage this flag to identify all merged PRs that have issues during the merge

Process

Classification:

Code

Tools:

Atlassian Jira, Github, Gitlab, Bitbucket

Intent:

The intent of this flag is to help engineering leads, project managers, compliance owners to get a sense of merged PRs:

1. That have not been approved by the right set of approvers in the code repository.

2. That have been approved by less than the required number of approvers in the code repository.

The first point is crucial because a merge approved by a wrong set-of people may mean that the code base is not comprehensively reviewed. 

Configurations:

1. Enable this check for PRs or PRs and Branches.
2. Enable auto-resolution settings and select "notifying via email" as the option, this will ensure ensure that the platform notifies the administrators and issues assignees for corrective measures.
3. The compliance settings for this flag is enabled by default (this will ensure the visibility of all the artefacts violating this flag in the compliance status report).

Note: A bunch of configurations in the VCS tool settings (Gitlab/Github/Bitbucket) is essential for the flag to work, refer to point 1 in this article for more details.