Flags deep dive: PR has process defects

When to use this Flag?

Leverage this flag to identify all PRs that have process defects e.g. reviews, approvals, merge conflicts, deviations from number of approvals before merge etc.

Process

Classification:

Code

Tools:

Atlassian Jira, Github, Gitlab, Bitbucket

Intent:

The intent of this flag is to reduce the time spent by tech leads and engineering managers in reviewing PRs to detect process defects that can lead to development bottlenecks, cause delays, and ultimately impact product quality. At times PRs that go undetected create documentation hassles and it takes a lot of time to extract their logs. Proactively identifying PRs with process defects can also avoid such situations. 

Configurations:

1. Configure the following for an open/merged PR:
   • Configure the thresholds for Open PRs (in terms of the creation of the PR).
   • Enable the "PR Approval check" condition to flag a open PR where the PR was approved without any review comments provided by the reviewer.
   • Enable the "PR review comment check" condition (with the configured threshold) to flag a open PR, if the author has not addressed comment as per the configured threshold.
   • Enable the "PR update check" condition (with the configured threshold) to flag an open PRs if the PR was not modified beyond the configured threshold (represents a stale PR).
2. Enable auto-resolution settings and select "reporting this flag as an issue in Jira" as the option, this will ensure that the platform automatically creates an issue in Jira with the problems selected in the flag.
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).