# Source: https://docs.snyk.io/implementation-and-setup/team-implementation-guide/phase-6-triages-ignores-and-fixes.md

# Phase 6: triages, ignores and fixes

## 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-and-setup/team-implementation-guide/phase-4-create-a-fix-strategy), you created a plan for prioritizing your Projects and issues. To implement this, 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. This allows you to 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 may see specific packages or vulnerabilities that you do not currently want to fix. This could be for a range of reasons, such as:

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

## Use the ignore feature

In each case, you can use the "ignore" feature to stop these from appearing each time you run a test.

{% hint style="info" %}
Confirm ignore with an Organization Admin (they may need to complete this step themselves).
{% endhint %}

When adding the ignore:

* Ensure you add a detailed reason, so the ignore reason is clear to others who see this issue.
* Set an expiration date for the ignore rather than having a permanent ignore. This is essential, as whilst the issue may not be fixable/relevant today, it should be reviewed regularly (monthly or quarterly) to see if it is possible to implement a fix.

{% hint style="info" %}
In **Settings-General** it's common to limit access to who can ignore an issue and require a reason.
{% endhint %}

By default, the **Organization Collaborator** role has permission to ignore issues, but this can be controlled per Organization in the **Settings** page (that is, restricted to **Organization admins** only).

See [Ignore issues](https://docs.snyk.io/manage-risk/prioritize-issues-for-fixing/ignore-issues) for more details.

##