> For the complete documentation index, see [llms.txt](https://docs.r.xyz/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.r.xyz/main/bug-bounty/overall/report-thread-overall-flow/report-thread-statuses.md).

# Report thread statuses

The report thread within the bug tracking system has several statuses that help track the progress and current state of each bug report. These statuses include:

* **Bug Reported:** This is the initial status when a bug report is submitted. It signifies that the report is awaiting review and action.
* **In Progress:** The status changes to "In Progress" when an organization user or a triager begins the review process or assigns it for resolution.
* **Closed:** Reports are marked as "Closed" once they are resolved, and the bug has been addressed satisfactorily.

These statuses serve as clear indicators of the current stage of bug report processing, ensuring transparency and effective communication among participants.


---

# 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.r.xyz/main/bug-bounty/overall/report-thread-overall-flow/report-thread-statuses.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.