= Overview Issue navigation is the incoming part of our issue. Classing and routing issues to the right team helps the customers or reporters to get their problems solved. = Workflow Where are the issues that need someone forwarding them? {F62} now click on the box showing "Workflow Issue Navigation" {F64} Now, you should see the "Issue Navigation Workboard" {F66} = Validating an Issue Reports that need to be validated, are in the 'Workflow Issue Navigation' (see above) 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 ==== Missing anything? Show you are now picking this up for requesting feedback. Drag it into the "feedback" coloumn. {F96} And open the issue by clicking the title. Scroll to the end and {F98} Select "Reassign / Claim" on the new input screen (red arrow). Add the reporter in the "Assigned to" (green arrow) field. now hit 'Submit'. ==== All seems fine? Drag it into the "Open for Testing" coloum. {F100} = Confirm an Issue Ready for ingame testing? Get a predictable game-state and start picking up an issue from "Open / Validated".

= Overview Issue navigation is the incoming part of our issue processing. Classing and routing issues to the right team helps the customers or reporters to get their problems solved. (Image here) = Navigate to the Workflow Where are the issues that need someone forwarding them? Short: {nav icon=eye, name=Phabricator > icon=briefcase, name=Projects > icon=folder, type=instructions, name=Workflow Issue Navigation } Hit the "eye" symbol in the top left corner and select "Projects" in the sidebar {F62, layout=left, size=full} now click on the box showing "Workflow Issue Navigation" {F674, layout=left, size=full} Now, you should see the "Issue Navigation Workboard" {F66, layout=left, size=full} = Tasks and Duties From there you have 3 options. ==== Validate You can [[ http://phab.starma.de/w/tester/issue_navigation/validate/ | Validate ]] issues that have been reported recently. ==== Confirm You can [[ http://phab.starma.de/w/tester/issue_navigation/confirm/ | Confirm ]] issues that have been validated and need someone to do the ingame testing on them. ==== Feedback You also have to keep an eye on the tasks you requested [[ http://phab.starma.de/w/tester/issue_navigation/feedback/ | feedback ]] from the reporter to add more information.

= Overview Issue navigation is the incoming part of our issue processing. Classing and routing issues to the right team helps the customers or reporters to get their problems solved. = Workflow Where are the issues that need someone forwarding them? {F62} now click on the box showing "Workflow Issue Navigation" {F64} Now, you should see the "Issue Navigation Workboard" {F66} = Validating an Issue Reports that need to be validated, are in the 'Workflow Issue Navigation' (see above) 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?(Image here) ==== Additionals= Navigate to the Workflow - Is there information about java-version or OS that may be required? (Especially on issues with the launcher itself or weird error-messages)Where are the issues that need someone forwarding them? ==== 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.Short: {nav icon=eye, use in mind!name=Phabricator > Do not upload 5 logs of 4MB each when they are zipped only 500kb.icon=briefcase, name=Projects > In this caseicon=folder, type=instructions, its easier to quote a part of the log (~20-30 lines) into the comment.name=Workflow Issue Navigation } ==== Client state - Does the client seem to be unmodified?Hit the "eye" symbol in the top left corner and select "Projects" in the sidebar Having someone state he has a fresh installation and{F62, layout=left, size=full} now click on the startup tells there were 200 blueprints processed is easy to see,box showing "Workflow Issue Navigation" 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?{F674, layout=left, size=full} Now, you should see the "Issue Navigation Workboard" This may also be added after reproducing it{F66, layout=left, size=full} ==== Missing anything?= Tasks and Duties Show you are now picking this up for requesting feedback. Drag it into the "feedback" coloumn. {F96} And open the issue by clicking the title. Scroll to the end and {F98}From there you have 3 options. Select "Reassign / Claim" on the new input screen (red arrow).==== Validate Add the reporter in the "Assigned to" (grYou can [[ http://phab.starma.de/w/tester/issue_navigation/validate/ | Validate ]] issues that have been arrow) fieldreported recently. now hit 'Submit'. ==== All seems fine? Drag it into the "Open for Testing" coloum.Confirm {F100}You can [[ http://phab.starma.de/w/tester/issue_navigation/confirm/ | Confirm ]] issues that have been validated and need someone to do the ingame testing on them. = Confirm an Issue Ready for ingame testing?==== Feedback Get a predictable game-state and start picking up an issue from "Open / Validated"You also have to keep an eye on the tasks you requested [[ http://phab.starma.de/w/tester/issue_navigation/feedback/ | feedback ]] from the reporter to add more information.