Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Project retests typically occur on a nightly or weekly basis, but you can also r

1. Log in to the Snyk Web UI and navigate to your Group and Organization.
2. Open a Project and find an issue card.
3. Select **Ignore across repository** on an issue card to create an ignore.
3. Select **Ignore** on an issue card to create an ignore.
4. Fill in the ignore information and confirm its creation. The issue will be updated and moved from **Open** to **Ignored**.\
\
If anyone loads the page before a retest, an indicator will appear and encourage retesting to capture policy or ignore changes.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -10,15 +10,15 @@ Conversion provides you with control over which ignores Snyk converts. For examp

The following scenario assumes that you have ignored issues in your Snyk Code Project prior to enabling Snyk Code Consistent Ignores.

If you have enabled the **Snyk Code Consistent Ignores** feature and have not performed a rescan since, in order for the **Ignore across repository** button to be active, it is possible that you need to [retest the Project](../../../../scan-with-snyk/snyk-code/manage-code-vulnerabilities/#retesting-code-repository). In most cases, the **Ignore across repository** button is active, and this step is not necessary.
If the **Ignore** button is inactive after you enable the **Snyk Code Consistent Ignores** feature, retest the Project.

## Convert individual ignore

In the Snyk Web UI, navigate to a Project and open an issue card that contains an issue that was ignored before enabling this feature.

A warning states that the ignore was created through the legacy system and is not consistent across the repository. All issues ignored before enabling the feature appear with this warning, so you can determine what ignore metadata must be converted and used as the source of truth.

To convert an issue from a Project-scoped to an asset-scoped ignore, click **Ignore across repository**.
To convert an issue from a Project-scoped to an asset-scoped ignore, click **Ignore**.

## How Snyk handles metadata

Expand Down
Loading