> 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/creating-a-bug.md).

# Creating a bug

Create a bug from test execution or from the Bugs section.

## Creating a bug

### Before you start

Collect the issue details you want to capture.

If possible, create the bug from a failing step so the execution context is included automatically.

You can create a bug during test execution or manually.

### From test execution

This is the recommended method.

1. Open a failing step during test execution.
2. Click **Create Bug**.
3. Review the pre-filled details.
4. Complete any remaining fields.
5. Click **Save**.

Test Manager pre-fills the bug with the test case name and relevant context.

### Manually

1. Open **Bugs** from the top navigation.
2. Click **Create Bug**.
3. Enter a title and description.
4. Set severity, priority, status, and assignee.
5. Click **Save**.

<figure><img src="https://95054152-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgQEgtjvk4zIWyVkgQ5o%2Fuploads%2FtlqBfSiyEG6AYE5Tu6rF%2FScreenshot%202026-07-01%20at%202.50.09%E2%80%AFPM.png?alt=media&amp;token=4eaccc6b-a368-4bb3-abcc-36f2a3e208f0" alt=""><figcaption></figcaption></figure>

### Expected result

The bug is saved with its own ID and lifecycle fields.

If you create it during execution, the bug also keeps the testing context that led to the issue.

### Next step

To understand how bugs move through resolution, see [Bug lifecycle](/test-context-manager-documentation/bug-tracking/creating-a-bug/bug-lifecycle.md).


---

# 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/creating-a-bug.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.