>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3600605. --> Reported by: [greggles](https://www.drupal.org/user/36762) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Security issues can be filed in the drupalcode gitlab instance even if they are not in the scope of getting a security advisory. We need a status for those.</p> <p>Additionally, it would be great to automatically add this label if a module does not match the policy.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Have a confidential issue in gitlab that is not in the security advisory policy, but it's not easy to see that with a quick glance and the current "security status" values are not applicable.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add a new status to the "security status" grouping called "not in advisory policy"</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>? Gitlab admin needs to do stuff?</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>yes.</p> <h3 id="summary-api-changes">API changes</h3> <p>n/a.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>n/a.</p>