-
Report should be named in a way that would identify the problem at the first sight. You have to write what’s the problem about in square brackets (which raid, class, etc.). For example: [Warrior] Bladestorm, [Ulduar - Thorim] Adds deal too much damage, [Warsong Gulch] wrong flag respawn timer.
-
Every bug has to be described thoroughly. “Quest X doesn’t work” is simply not enough. You have to write what exactly is happening and what should happen.
-
Every bug should be reported with the following pattern:
Decription: How it works: How it should work:
-
To make things get fixed faster, you should write the steps to reproduce said bug under “Steps to Reproduce”.
-
“Additional Information” section should contain IDs of every spell, item, game objects, etc. You need to add them via link: http://db.darkwizard.pl/. Additionally, you should show here evidences that this is indeed a bug, not an intended action.
-
Every report has to be placed in a right category. ‘Exported’ category is for bugs that were exported from our previous BugTracker, you musn’t use it.
-
Reports that do not meet requirements listed above can be closed without further investigation.
-
Notifications
You must be signed in to change notification settings - Fork 42
Elaatu/issues
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
Sunwell Bug Tracker. Feronis and Angrathar share the core, so all bugs will be fixed on both realms.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published