---
title: "Defect Prioritization Process"
slug: "defect-prioritization-process-1"
updated: 2024-03-18T20:11:45Z
published: 2024-03-18T20:11:45Z
canonical: "docs.catchpoint.com/defect-prioritization-process-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Defect Prioritization Process

<span contrast="auto">This article highlights how a Product related issue (defect) is determined and prioritized.</span>

<span contrast="auto">When a </span><span contrast="auto">product-related support ticket</span><span contrast="auto"> is</span><span contrast="auto"> raised</span><span contrast="auto">,</span><span contrast="auto"> the </span><span contrast="auto">steps</span><span contrast="auto"> below</span><span contrast="auto"> </span><span contrast="auto">are followed</span><span contrast="auto">:</span><span ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:259}"> </span>

1. The Technical Account Manager (TAM) handling the issue investigates to confirm if the issue is a Product defect.
2. If deemed a defect, the issue is then escalated to our Engineering Team.
3. Product Management Team (PM) will assign a status and priority to the defect depending on several factors such as dependencies between features, product affected and scope of impact.


<span contrast="auto">Defects will fall under one of the three s</span><span contrast="auto">tatus</span><span contrast="auto">es</span><span contrast="auto">:</span><span ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:259}"> </span>

1. **Release Targeted** - Defects under this category have been assigned to a release and is expected to be fixed in one to three releases.
2. **Catchpoint Backlog** - Defects under this category do not have an ETA and are not expected to be fixed within the next three releases 
3. **Will not fix**  – Defects under this category will not be fixed for one of the two reasons:

- <span contrast="auto">Defect is deemed to have low or isolated   impact</span><span   ccp-props="{&quot;201341983&quot;:0,&quot;335551550&quot;:1,&quot;335551620&quot;:1,&quot;335559737&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span>
- <span contrast="auto">An upcoming feature or update will make the fix   unnecessary; you will receive updates on new feature/update on our   release notes.</span><span   ccp-props="{&quot;201341983&quot;:0,&quot;335551550&quot;:1,&quot;335551620&quot;:1,&quot;335559737&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span>

<span ccp-props="{&quot;201341983&quot;:0,&quot;335559685&quot;:360,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span>

*<span contrast="none">If you have any concern regarding any of the statuses assigned, please reach out to your Customer Success Manager (CSM) or Account Executive (AE).</span>*<span ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:259}"> </span>