> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-6-triages-ignores-and-fixes.md).

# Phase 6: Triages, ignores, and fixes

Phase 6 of the Snyk team implementation: triage, prioritize, ignore, and fix vulnerabilities in your backlog

## Tips for deciding on prioritization

After you implement a strategy to prevent new issues from entering your repositories, whether blocking builds or running in a non-blocking/advisory mode, the next step is to prioritize and start fixing issues in your backlog.

* In [Phase 4: Create a fix strategy](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-4-create-a-fix-strategy.md), you created a plan for prioritizing your Projects and issues. To implement this plan, you can schedule regular meetings with development team leads to assist them with this process.
* If you use Jira Cloud, you can download and install the [Snyk Security in Jira Cloud](https://marketplace.atlassian.com/apps/1230482/snyk-security-in-jira-cloud) plugin from the Atlassian Marketplace. You can then view information on your Snyk vulnerabilities directly in Jira and use Jira Automation to create new tickets when new vulnerabilities are identified.

## When should you ignore an issue?

When deciding your priority for fixing issues, you can find specific packages or vulnerabilities that you do not want to fix now. The reasons vary, for example:

* The fix introduces breaking changes, and you do not have time to fix them.
* This vulnerability does not apply to you for an environmental/contextual reason.

## Use the ignore feature

In these cases, use the ignore feature to stop these issues from appearing each time you run a test.

{% hint style="info" %}
Confirm the ignore with an Organization Admin. If only Organization Admins can ignore issues in your Organization, the Organization Admin must complete this step.
{% endhint %}

When adding the ignore:

* Add a detailed reason so that others who see this issue understand why it is ignored.
* Set an expiration date for the ignore rather than making it permanent. This is essential: even if the issue is not fixable or relevant today, review it regularly (monthly or quarterly) to check whether a fix is now possible.

{% hint style="info" %}
In **Settings** > **General**, it is common to limit who can ignore an issue and to require a reason.
{% endhint %}

By default, the **Organization Collaborator** role has permission to ignore issues. You can restrict this permission to **Organization Admins** only on the **Settings** page of each Organization.

For more details, visit [Ignore issues](https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/ignore-issues).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-6-triages-ignores-and-fixes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
