> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/core-concepts/issues/issue-error-codes.md).

# Issue Error Codes

Reviewers may assign error codes to tasks they review. This way, instead of writing a issue by hand, they can affix a pre-built error code detailing the nature of the problem with the task. (e.g. *Slightly incorrect, Very Incorrect, Missing*, etc.)

## Setting Up Error Codes

To set up error codes in your project, navigate to *Settings -> General* and enable the toggle next to *Error Codes:*

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FhuWuqzMxgyrlDppMRlva%2Fimage.png?alt=media&amp;token=e47e3495-b4bc-42aa-ba0b-f5fabf4566b3" alt=""><figcaption></figcaption></figure>

From this interface, you can add, remove, and edit error code categories, and add individual error codes in them.

To add a new error code category, click on the "+ Add Error Code" button. To edit the name of an existing one, click on the *pen* icon. To delete, click on the *trash can* icon.

To create an error code, type the name of the error code in one of the categories, then press Enter. There is no limit to how many error codes a category may contain. Press *Save* at the bottom of the page to save your error codes.

To change the order of error codes, drag their tags within a category, then click **Save**. The codes appear in the new order when selecting error codes on issues.

## Assigning Error Codes during Review

There are currently two ways to assign error codes to assets: through issues or when rejecting a task during review.

In the *Select errors* field, type to filter the list and use the arrow keys to highlight an error code. Press *Space* or *Enter* to select or unselect it. Press *Tab* to close the list and move to the next field, or *Shift+Tab* to move to the previous field, without selecting the highlighted error code. The *Space* key selects error codes, so spaces cannot be entered in the search field.

### Error Codes on Issues

During review, or any other stage and role in which issues can be placed, click on the "issue" icon in the top right and click on the asset where you'd like to place the issue, then pick the error code category and an error code:

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FlvOAVB1mNvWyuZ3DQ8Tj%2Fimage.png?alt=media&amp;token=0f89c2b9-58f9-4b57-aa33-b087e1c6f4c2" alt=""><figcaption></figcaption></figure>

After selecting at least one error code, you can leave the issue text blank. Click *Open Issue* in the dialog, or click the send arrow on an issue pin or in the *Issues* sidebar.

Alternatively, you may create issues directly on objects by selecting the object and pressing on the letter I on your keyboard, and assign error codes that way.

### Error Codes on Rejection

When in a review stage, click on the *Reject* button at the top right to mark the task as rejected. If the task contains no issues, a popup will appear.

Pick a category and an error code as shown in the previous section and click on *Open Issue & Reject*. You can leave the issue text blank.


---

# 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.imerit.net/core-concepts/issues/issue-error-codes.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.
