# Processing bug reports

### General Information

Once a bug report has been approved by your Team, it will be sent to the already configured todo-channel ([/todo-channel](/commands/owner-commands/todo-channel.md)). There a Developer or higher can process the suggestion.

### Requirments

* The User must have either the Developer ([/dev-role](/commands/owner-commands/dev-role.md)) or Manager Role ([/manager-role](/commands/owner-commands/manager-role.md)), or be an Administrator

### How to use

Once a bug report has been sent to the ToDo-Channel it will look something like this:

![](https://media.discordapp.net/attachments/731166978806644827/937573102387335218/Bug_Reports_To-Do_Channel.png?width=702\&height=702)

1. **Reserve the Ticket**\
   Developers can reserve the bug report. This is mainly for organizational purposes. In addition, when an update is published, the developer is credited for fixing the bug report.
2. **Re-classify as Low Severity** \
   This will allow Developer to re-classify their bug report to a Low Severity.
3. **Re-classify as Medium Severity** \
   This will allow Developer to re-classify their bug report to a Medium Severity.
4. **Re-classify as High Severity**\
   This will allow Developer to re-classify their bug report to a High Severity.
5. **Send it in the publishment Queue**\
   As soon as a bug is fixed by a Developer, they can move it to the publishment queue. This deletes the suggestion from the channel and moves it to the final stage. As soon as a game update is now published, this bug report is attached as implemented. This action can not be undone.
6. **Publish it immediately**\
   Unlike the "Publish Queue" button, this is not intended for game updates but rather for game hotfixes. The suggestion is published directly as a single update.
7. **Delete the suggestion**\
   If the developer decides that you do not want to fix the bug, you can delete it using the "Delete" button. **Important: The user will not be informed that the bug report has been deleted.**


---

# Agent Instructions: 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:

```
GET https://builderman.theravenhub.com/commands/developer-commands/processing-bug-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.