Flags deep dive: Branch/PR has commits mapped to issues from incorrect projects

When to use this Flag?

Leverage this flag to identify all PRs/Branches that have commits mapped to issues/tickets from incorrect project.

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 PRs that are born out of issues originating from incorrect projects (which may mean that the code base committed by the developer may carry unnecessary business logic that may result in downstream issues). 

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 2 in this article for more details.