> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/bug-tracking/creating-a-bug/bug-lifecycle.md).

# Bug lifecycle

## Bug lifecycle

Bugs move through a defined status workflow.

| Status      | Meaning                                                       |
| ----------- | ------------------------------------------------------------- |
| Open        | Bug is newly reported and not yet being worked on.            |
| In Progress | A developer or tester is actively investigating or fixing it. |
| Resolved    | A fix has been applied and is ready for verification.         |
| Closed      | The fix has been verified and the bug is no longer active.    |
| Reopened    | A previously closed bug needs more work.                      |

To update the status:

1. Open the bug detail page.
2. Click the status field.
3. Select the new status.

All status changes are recorded in the **History** tab.


---

# 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://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/bug-tracking/creating-a-bug/bug-lifecycle.md?ask=<question>&goal=<endgoal>
```

`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.