Please Read First - Bug Reporting Template
Posted: Tue Dec 02, 2008 1:27 am
How to Report a Bug
So, you are here to report a bug eh? We appreciate you reporting your concerns to us. UO Second Age strives to be as closely T2A ERA accurate as possible. We also want you to have an enjoyable playing experience free from any bugs or pesky errors. Please read the following information before reporting an issue for tips to help expedite the Bug Reporting process.
When reporting bugs to our development team, providing precise and clear information about the issue, your environment, steps to recreate the issue, and what the expected outcome should be will greatly help our team pinpoint the problem and provide a speedy resolution. Providing link references to things you point out to be ERA inaccurate greatly helps speed up staff research into this area also.
Bug Reporting Template
It is recommended to use the following template when reporting problems here. Explanations will be given below. An example will be dislayed in the next post within this thread.
REPORTED ISSUE:
ISSUE DETAILS:
ENVIRONMENT DETAILS:
STEPS TO RECREATE:
EXPECTED RESULTS:
DATE REPORTED:
STATUS: Open
DATE STATUS CHANGED:
Recommended Reporting Method
1. When posting a bug, please create a new thread for that specific issue. This helps internal tracking efforts to ensure each issue is handled properly.
2. In the Subject line, enter the part of the game the issue affects and a short description of the issue (i.e. Cooking - Barbequing Egg Results in Baked Bread).
3. Paste the above template into the Message Body Area.
4. In the REPORTED ISSUE area, copy the subject line and paste or retype it into this field. This field is intended for a very short description of the issue only at base level.
5. In the ISSUE DETAILS area, describe the issue in as much detail as possible. However, do not include any steps to recreate the problem or what you expect should happen. That will be done later in the form.
6. In the ENVIRONMENT DETAILS area, include any environment specific information that could help solve the problem. For example, your windows version, computer specifications, UO client version, ETC.
7. In the STEPS TO RECREATE area, describe the best you can the exact steps to recreate the problem. If you must have a certain skill level or certain item equipped, be sure to explain. This area will require the most information for you to fill out. This area will also help solve the problem the fastest.
8. In the EXPECTED RESULTS area, describe what should happen when your steps to recreate are taken by a player. If possible, please provide reference links for things you reference to be ERA inaccurate.
9. In the DATE REPORTED area, enter the date the issue was reported on this message board.
10. In the STATUS area, enter Open. This will be updated by staff members as the issue is tested, confirmed, resolved, or cancelled.
11. Leave the DATE STATUS CHANGED AREA blank. This area will be updated by staff mebers as the issue moves through the QA and development processes.
Thank you for reading this guide. Following these tips will greatly help our team and we thank you for your effort in advance.
So, you are here to report a bug eh? We appreciate you reporting your concerns to us. UO Second Age strives to be as closely T2A ERA accurate as possible. We also want you to have an enjoyable playing experience free from any bugs or pesky errors. Please read the following information before reporting an issue for tips to help expedite the Bug Reporting process.
When reporting bugs to our development team, providing precise and clear information about the issue, your environment, steps to recreate the issue, and what the expected outcome should be will greatly help our team pinpoint the problem and provide a speedy resolution. Providing link references to things you point out to be ERA inaccurate greatly helps speed up staff research into this area also.
Bug Reporting Template
It is recommended to use the following template when reporting problems here. Explanations will be given below. An example will be dislayed in the next post within this thread.
REPORTED ISSUE:
ISSUE DETAILS:
ENVIRONMENT DETAILS:
STEPS TO RECREATE:
EXPECTED RESULTS:
DATE REPORTED:
STATUS: Open
DATE STATUS CHANGED:
Recommended Reporting Method
1. When posting a bug, please create a new thread for that specific issue. This helps internal tracking efforts to ensure each issue is handled properly.
2. In the Subject line, enter the part of the game the issue affects and a short description of the issue (i.e. Cooking - Barbequing Egg Results in Baked Bread).
3. Paste the above template into the Message Body Area.
4. In the REPORTED ISSUE area, copy the subject line and paste or retype it into this field. This field is intended for a very short description of the issue only at base level.
5. In the ISSUE DETAILS area, describe the issue in as much detail as possible. However, do not include any steps to recreate the problem or what you expect should happen. That will be done later in the form.
6. In the ENVIRONMENT DETAILS area, include any environment specific information that could help solve the problem. For example, your windows version, computer specifications, UO client version, ETC.
7. In the STEPS TO RECREATE area, describe the best you can the exact steps to recreate the problem. If you must have a certain skill level or certain item equipped, be sure to explain. This area will require the most information for you to fill out. This area will also help solve the problem the fastest.
8. In the EXPECTED RESULTS area, describe what should happen when your steps to recreate are taken by a player. If possible, please provide reference links for things you reference to be ERA inaccurate.
9. In the DATE REPORTED area, enter the date the issue was reported on this message board.
10. In the STATUS area, enter Open. This will be updated by staff members as the issue is tested, confirmed, resolved, or cancelled.
11. Leave the DATE STATUS CHANGED AREA blank. This area will be updated by staff mebers as the issue moves through the QA and development processes.
Thank you for reading this guide. Following these tips will greatly help our team and we thank you for your effort in advance.