If you have issues with any aspect of these standards, feel free to leave a comment (Comments button above).
Bug vs. Usability vs. Feature Request
If you're not sure what type of issue you've found, here's a basic guideline.
A bug is an error with existing code. If you know something is explicitly supposed to work one way and it does not, it's a bug.
Example #1: The Vs. Comprehensive Rules state that flipping a location interrupts successive passes. Playing in the game, you've found it does not. File it as a bug.
Example #2: The website has a link that says it goes to the Trades page. Clicking it, you find yourself at a 404 Page Not Found error. File it as a bug.
Usability is hard to define. Generally a usability issue is something that makes an interface less efficient, effective, or satisfying. (Follow link for a larger discussion.) It differs from a regular bug by not being explicitly incorrect. The feature works, it just could work better.
Example #1: Most popups in a program have the "OK" response on the left and the "Cancel" response on the right. You've found one that switches the order and thus can cause mis-clicks with users. File it as a usability issue.
A Feature Request is a request for some functionality that doesn't exist yet within the program.
Example #1: You believe that trading would be much improved if there was an Auction House within the game. Nothing like that exists currently, so you file it as a feature request.
Color Legend
Issues have a background color that helps identify the state of the issue.
| This is an Open issue. A newly found bug that hasn't been addressed yet. |
| This is a Resolved issue. The developers have stated that the bug is fixed, but players have not independently verified the fix yet. |
This is a Closed issue. The problem has been verified as fixed. |
Comments (0)
You don't have permission to comment on this page.