Builderman
  • ℹī¸Overview
    • What is Builderman?
  • đŸĨ‡First Setup
    • Pre-Requirments
    • Channels & Permissions
    • Custom Settings
  • 📄Commands
    • Default Users
      • /suggest
      • /report
      • /help
      • /invite
    • Approvers
      • Incoming suggestions
      • Incoming bug reports
    • Developers
      • /queue
      • Processing suggestions
      • Processing bug reports
    • Managers
      • /list-games
      • /add-game
      • /delete-game
      • /publish
      • /blacklist
      • /status-embed
    • Administrators
      • /holding-channel
      • /todo-channel
      • /poll-channel
      • /update-channel
      • /update-ping
      • /manager-role
      • /dev-role
      • /approver-role
      • /blocked-role
      • /scope
      • /language
  • ❔FAQ
    • Why does the bot not work after the migration?
    • Slash-Command don't appear
    • What are "scopes"?
    • What does the report Function?
    • My Files are not accepted
Powered by GitBook
On this page
  • General Information
  • Requirments
  • How to use

Was this helpful?

  1. Commands
  2. Developers

Processing bug reports

PreviousProcessing suggestionsNextManagers

Last updated 3 years ago

Was this helpful?

General Information

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

Requirments

  • The User must have either the Developer () or Manager Role (), or be an Administrator

How to use

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

  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.

📄
/todo-channel
/dev-role
/manager-role