> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/test-context-manager-documentation/bug-tracking/overview.md).

# Overview

Learn how bug tracking works in Test Manager.

Test Manager includes a built-in bug tracking system.

### What this feature does

Use bug tracking to capture issues found during execution and manage them through resolution.

### What's included

It integrates directly with test execution.

You can create bugs:

* from a failing test step
* from the **Bugs** section

Each bug gets a human-readable ID automatically.

Examples include `BUG-001` and `BUG-002`.

Each bug also includes status, severity, priority, assignee, and history.

### What's not included

Bug tracking does not replace test design or execution records.

Use test cases, plans, and runs for those workflows.

<figure><img src="https://95054152-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgQEgtjvk4zIWyVkgQ5o%2Fuploads%2FA4iu6WMMQmGTNSa9nvZd%2FScreenshot%202026-07-01%20at%202.48.20%E2%80%AFPM.png?alt=media&amp;token=86301896-c638-4b69-9559-2cb2afb8e79d" alt=""><figcaption></figcaption></figure>


---

# 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.mozark.ai/test-context-manager-documentation/bug-tracking/overview.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.