General

Profile

Home

Create new ticket

Activity

Checklist

Rule 1: Search Function

Please ensure that you first use the search function to check whether your issue has already been reported. If a ticket exists that describes the same issue, you can help by adding more information via a comment. If you cannot find any existing tickets, or think your issue may relate to a different problem from existing tickets, please create a new one.

Rule 2: English only

All tickets must be in English only. This ensures that everyone has the opportunity to understand the issue. Tickets written in any other language will be closed.

Rule 3: Clear and descriptive title

The title of a ticket should always describe what the issue is about as briefly and as concisely as possible. It is important that you or others can use the search function, read the title and know as soon as possible what the issue is about and whether it is your own problem or not.

"Bug in Icecrown Citadel" or "Lord Marrowgar not working", for example, are far too broad.
"[ICC] Lord Marrowgar - Bone Storm Does Too Much Damage", on the other hand, aptly describes the bug.

Rule 4: Only 1 bug per ticket

If several errors are processed in a ticket, it can quickly become confusing. Therefore, please create a separate ticket for each bug.

Rule 5: Links

Please post the corresponding links from the RG database (alternatively from Wowhead) to quests, creatures, items, spells etc. related to your problem in your ticket. The ticket can only be edited once all links have been specified.

Example: "Too few cobalt resources available - here is the link: https://db.rising-gods.de/?object=189978"

Rule 6: Sources

In order for a bug to be fixed, we need to know exactly how the related behaviour worked on retail. Therefore, please search for sources that confirm your statements in advance. Other private servers as well as statements like "I played WotLK X years ago, I definitely remember that" are not enough evidence of a problem.

A source is needed for all errors. For example, information is provided here:

An archive for pages that are no longer available can be found at: https://archive.org/web/

Rule 7: Exact circumstances

In order to fix a bug, we must first be able to reproduce it. Please include detailed information about the circumstances with your ticket. Important information could be, for example:

  • In-game coordinates (X/Y position)
  • Times
  • Level of difficulty of the instance
  • Talent distribution
  • etc.

Example: Lord Marrowgar (10 man heroic) didn't use bone storm in his second phase on 26/04/2016.

Rule 8: Comments

The rules of this checklist also apply to comments. Therefore please pay attention to neutral reporting, sources, links, etc.
Comments like "push", "still doesn't work", "totally annoying, please fix!!1!" that don't help to solve the problem are not permitted and will be deleted.

Ticket statuses

New

This error still has to be checked. If you have additional information, you can add it to the ticket at any time by commenting.
Only when all links have been provided, the described situation has been clearly identified as erroneous by the sources and the error has been reproduced2 will the ticket be confirmed.

Feedback

The ticket currently cannot be processed because the information relevant for the reproduction of the error is missing. If you have created the ticket or if you have this information, please add it, otherwise the ticket will be rejected after one week. You should be able to find out what this information is by reading the comments below the ticket (if not, please ask!).

Research

The reported bug could be reproduced, but it is not sure if it is actually a bug and/or what the state on the official server was like during the patch Dragonblight currently emulates. In order to be able to process the ticket further, it is therefore necessary to search for sources that present the status of that patch on retail. If you want to help, you can search for sources and add a comment (don't forget the link to the source!).

Confirmed

The error was examined and identified as such. Please note that processing may take some time depending on the complexity and priority of the error.

In Progress

The ticket is currently being processed by the assigned tester or developer.

QA

A developer has applied a fix for the problem on the (for players inaccessible) test server, which now has to be checked for functionality by a tester. This fix will not work on the game server yet.

Code-Review

A developer has prepared a fix for the problem which now has to be reviewed by other developers.This fix will not work on the game server yet.

Code-Review & QA

A developer has applied a fix for the problem on the (for players inaccessible) test server, which now has to be checked for functionality by a tester and reviewed by another developer. This fix will not work on the game server yet.

Ready for merge

The error was fixed on the test server. However, preparatory changes must still be made so that the fix can be scheduled for the next server update.
Attention: This fix is currently not on the game server.

Scheduled for next update

The bug has been fixed on the test server and will be installed on the game server with the next server update.
Attention: This fix is currently not on the game server.

Resolved

The bug was successfully fixed on the game server. If the bug persists, please create a new ticket. Comments in the old ticket will be ignored.

Closed

The situation described in the ticket is not a malfunction or cannot be reproduced.
If you can disprove the reason for the rejection (e.g. with another source or a new / more detailed reproduction guide), please create a new ticket with reference to the old one. Comments in a closed ticket will be ignored.

Duplicate

The ticket is a duplicate. The error is already handled in another ticket, which is linked as a related issue. Comments in a ticket marked as duplicate will be ignored.