= Validating an Issue
{F102, float, size=full} Reports that need to be validated, are in the column "New / Unconfirmed"
It is now up to you, to do a sanity check on this report.
Things you should check in any case:
==== Duplicate
- Do we already have an issue handling this case?
search for a few relevant words that are related to that issue
==== Subject
- Does the subject describe the issue in short and have all information you need to recognize it?
==== Description
- Can you easily imagine and understand the steps you need to trigger the bug?
==== Priority
- Does it match the Priority classification matrix?
==== Gamemode
- Does the gamemode match the description?
==== Additionals
- Is there information about java-version or OS that may be required?
(Especially on issues with the launcher itself or weird error-messages)
==== Attached Files
- are files attached in a quickly accessible format?
Bad: .zip files instead of direct logs
Good: log.x.txt directly attached
But keep effort vs. use in mind!
Do not upload 5 logs of 4MB each when they are zipped only 500kb.
In this case, its easier to quote a part of the log (~20-30 lines) into the comment.
==== Client state
- Does the client seem to be unmodified?
Having someone state he has a fresh installation
and the startup tells there were 200 blueprints processed is easy to see,
and can really save a lot of work -
tell user to re-add logs of a Predictable Game State then
==== Category
- Can you set it to match a category?
This may also be added after reproducing it
== All seems fine?
Drag it into the "Open for Testing" coloum.
{F100, size=full}
== Missing anything?
Read the [[ http://phab.starma.de/w/tester/issue_navigation/feedback/ | Feedback ]] section.