Step 1:
While in-game, check carefully that what you have found is really a bug and not just, for example, some lower rank of the ability or spell. With wrong information you would create a useless report which would just waste testers’ time and force them to deal with a non-existent issue. This obviously results in delaying resolution of reports containing real bugs and errors.
Step 2:
If you have followed step 1 and truly found a bug, open TwinHead in your browser and look up the bugged spell, ability, item… For example: Database – Spells – Class Skills – Druid – Balance – Wrath. Always look for the highest possible rank available in-game. Open the “Issues” tab and check whether there is not a report already created. If there is, look at its details and if it does not contain information relating to your issue, add what you have found to the comments and do not create a new report.
Note: To create a report, you must be an authorized user.
Step 3:
If there is no report concerning the bug you have found, it is up to you to create it. Under the description of every spell, ability, item etc. there is the option “Contribute” and under this option there is a text box with tabs. The only one important to you at this moment is “Create Issue”.
Here you describe the bug in the best way you can (see the paragraph “What the report should contain” below) and submit it by clicking on “Submit”.
Step 4:
Watch your report and add any additional information you find to the comments. In case of any problems with the report, contact only the tester that has changed status of the report. If it has not been changed yet contact anybody from the Test team on IRC.
What the report should contain:
Firstly you should provide a thorough description of the problem. If you write something like “It does not do any damage”, your report will be ignored and deleted/closed. Your report should also contain screenshots: if the spell Wrath does not do any damage, it is essential to attach a screen of the combat log. In case of, for example, some NPC and its encounter you are supposed to add a link to the description of this encounter containing information from official servers (ideally written by Blizzard itself). This applies to every report; several specific rules are to be found below.
– Quests:
They do not fall under the Test team. The best thing to do when reporting quest is to add a video with a player completing this quest or comments from official servers or WoWhead (it is enough to copy them from there with their author’s name). It is also necessary to provide links to any Game Objects, Quest Items, NPCs or any other things related to the quest (or their IDs). Any bugs of Game Objects, Items or NPCs which have to be fixed in order to fix the quest itself should be reported as a quest bug and not separately.
– Spells, abilities, talents, glyphs:
These reports should also contain a formula for damage/healing calculation. If you cannot find it, write it in the report (this applies to any report you create). A description from official servers with information how the spell, ability, talent or glyph should work is a must.
– Bosses, NPCs:
Regarding bosses the report should describe how the boss should work, what it should do and what it does not do during its encounter. Information from official servers is of course necessary. If you want to report an NPC related to a quest, do so by reporting the quest itself, not the NPC.
– General notice:
EVERY report should contain information about how the reported thing works (or does not work) on Twinstar and how it should work according to Blizzard.
What the report should NOT contain:
Descriptions like “It does not work” and similar, vulgarities, wrong screenshots or links, comparison of two or more free servers. All unsatisfactory reports will be closed.
Status legend:
New – A new report created by a player
Canceled – The player who created the report closed it or it was closed by a tester/DEV
Need Info – The report does not contain enough information to test the bug or fix it.
Confirmed – A tester confirmed the report. It is a report with enough information and what it describes is really a bug.
Duplicate – The bug has already been reported.
Not a bug – What the report describes is not a bug.
Fixed – The bug was fixed and the fix is going to be applied on live servers with the nearest update.
Wont fix – The bug cannot be fixed for now.
Reopened – This only concerns reports which were closed as fixed, but the fix did not work or the bug was found again.