> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder-2021.1/system-wide-settings/defect-parties.md).
# Defect Parties
As part of [system-level settings](/enate-help/builder/builder-2021.1/system-wide-settings.md) you can add and edit defect parties, so that when a work item goes wrong, service agents can add defects against the parties at fault.
### **Configuring Defects**
To configure new or edit the migrated defects click the edit link on a Service Line and expand the new advanced settings.
Here you can configure up to three levels of defect categories, and you can even mix-and-match some that are only a single level while others have multiple levels.
The defects applied to a Work Item is shared with any related Cases/Tickets and Actions (just like Custom Data, Files, Contacts, etc). So a defect added to an Action will also show on its parent Case. If that Case was launched by a Ticket then they would also show on that Ticket. Likewise if a Defect is added to a Ticket then it shows on the Case if one is launched from it.
When editing a defect category, you are also able to see its activity history by clicking on the Show Activity button. You can see when the defect category was created and by who, as well as if any edits have been made to the defect category, when they were made and by who.
Defect Parties can be localised and managed in the [Localisations page](/enate-help/builder/builder-2021.1/adding-localisations.md).
### **Warehouse aspects of the Defects changes:**
* In the data warehouse only the ‘hidden’ value was exposed with no way of getting the Display Value. Now there is just a single value defined.
* The warehouse contains the Defect Categories even if they are not referenced by a Work Item yet.
* The warehouse contains the localised Display Values in the usual Localisations table
* See separate “Breaking Changes” document for technical details of the new Warehouse database structure.
### **Migration of Defects data**
* Defect Categories that are on a Case OR Ticket are migrated to a single list on the Service Line – **this should be validated manually after the migration has been completed**.
* Note for customers migrating from version prior to v2019.4: Some customers may have some misconfigured Defect Categories created in older versions of the product. For example, it may be that they have have a Defect Categories of ‘(Select)’ which incorrectly does not have a value defined ending in ‘.Blank’ (perhaps a typo of ‘,Blank’) – as such this would be considered a valid category for the user to select in 2019.3 and below, and so this will be migrated over to later versions as a valid defect category. Customers may wish to correct or delete such unwanted defect values, something which can easily be achieved in Enate Builder.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.enate.net/enate-help/builder/builder-2021.1/system-wide-settings/defect-parties.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.