Issue Summary

GitHub Advanced Security Secret scanning manually created patterns that find vulnerabilities are not closed when the secret scanning pattern is deleted.

Steps to Reproduce

1. Create a password rule for secret scanning in GitHub
2. Introduce secret scanning alert in GitHub. You will see the vulnerability in Jira Security page
3. Delete the password rule from GitHub. This will remove the alert from GitHub as well.

Expected Results

Vulnerabilities to be removed from Jira Security

Actual Results

 You will see the vulnerability as open in Jira Security

Workaround

Step 1: Disconnect the Organization:

1. In Jira, select Apps, then Manage your apps.
2. Select GitHub for Jira, then Get started.
3. Locate the organization you’re having issues with, select the more actions icon (…), then choose Disconnect.
4. Confirm by selecting Disconnect again.

Step 2: Reconnect the Organization:*

1. Click on Connect a GitHub organization, then Connect GitHub Cloud.
2. Select Continue.
3. Choose GitHub Cloud, then click Next.
4. Enter your GitHub username and password, then Sign in.
5. Locate the organization you wish to connect to Jira, then select Connect.
6. Once the connection is complete, select Exit set up.

After reconnecting, please wait for the backfill process to complete. This will ensure all your GitHub security data is up to date in Jira.

Remember that, by default, the backfill process will sync only the last 6 months of data. You have to manually specify the start date to get it to resync data that is more than 6 months old.