= 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) in the Coloumn "New / Unconfirmed" {F102} 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". ==== Claim it {F104} Open one or two issues in a second tab (usually ctrl + click). {F98} Select "Reassign / Claim" on the new input screen (red arrow). Add yourself in the "Assigned to" (green arrow) field. A comment is optional. ==== Test it Get in the latest dev-build and start with the supplied steps to reproduce the issue. == Confirmed Issue happens as described ==== Update workflow Drag it from "Open" to "Confirmed / Validated" {F108} ==== Add the result When you were testing a single issue or needed to adjust something to make it happen, its easiest to add your outcome directly {F106} Now update/add the testing results {F110} Make sure you have the correct build in the field. Type only the version number in the last tested version field, nothing else. Also add you and the people that tested together with you in the "assigned tester" field. ==== Send them to development In case you confirmed more than one issue in your testing run and they all were happening exactly as described, you can confirm them in one pass. If you do not own all tasks in that column, filter the others {F114} and go to the confirmed "workflow column" and open the drop-down. {F112} Now select "Batch edit Tasks.." Check the list on top, to make sure you have the issues in you want. Now adjust the actions list like this: {F116} Change Status: in queue (Game) Now hit "Update Tasks" Herald will see the task, pick it up, and adjust workflows accordingly. You do not have to care about other settings in the issue.

= 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? Short: {nav icon=eye, name=Phabricator > icon=briefcase, name=Projects > icon=folder, type=instructions, name=Workflow Issue Navigation } {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) in the Coloumn "New / Unconfirmed" {F102} 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} == Missing anything? Read the Feedback section. = Confirm an Issue Ready for ingame testing? Get a predictable game-state and start picking up an issue from "Open / Validated". ==== Claim it {F104} Open one or two issues in a second tab (usually ctrl + click). {F98} Select "Reassign / Claim" on the new input screen (red arrow). Add yourself in the "Assigned to" (green arrow) field. A comment is optional. ==== Test it Get in the latest dev-build and start with the supplied steps to reproduce the issue. == Confirmed Issue happens as described ==== Update workflow Drag it from "Open" to "Confirmed / Validated" {F108} ==== Add the result When you were testing a single issue or needed to adjust something to make it happen, its easiest to add your outcome directly {F106} Now update/add the testing results {F110} Make sure you have the correct build in the field. Type only the version number in the last tested version field, nothing else. Also add you and the people that tested together with you in the "assigned tester" field. ==== Send them to development In case you confirmed more than one issue in your testing run and they all were happening exactly as described, you can confirm them in one pass. If you do not own all tasks in that column, filter the others {F114} and go to the confirmed "workflow column" and open the drop-down. {F112} Now select "Batch edit Tasks.." Check the list on top, to make sure you have the issues in you want. Now adjust the actions list like this: {F116} Change Status: in queue (Game) Now hit "Update Tasks" Herald will see the task, pick it up, and adjust workflows accordingly. You do not have to care about other settings in the issue. == Failed to reproduce Issue happens as described = Feedback 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 yourself in the "Assigned to" (green arrow) field. Add a comment requesting for details and what details you need, now hit 'Submit'.

= 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) in the Coloumn "New / Unconfirmed" {F102} 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". ==== Claim it {F104} Open one or two issues in a second tab (usually ctrl + click). {F98} Select "Reassign / Claim" on the new input screen (red arrow). Add yourself in the "Assigned to" (green arrow) field. A comment is optional. ==== Test it Get in the latest dev-build and start with the supplied steps to reproduce the issue. == Confirmed Issue happens as described ==== Update workflow Drag it from "Open" to "Confirmed / Validated" {F108} ==== Add the result When you were testing a single issue or needed to adjust something to make it happen, its easiest to add your outcome directly {F106} Now update/add the testing results {F110} Make sure you have the correct build in the field. Type only the version number in the last tested version field, nothing else. Also add you and the people that tested together with you in the "assigned tester" field. ==== Send them to development In case you confirmed more than one issue in your testing run and they all were happening exactly as described, you can confirm them in one pass. If you do not own all tasks in that column, filter the others {F114} and go to the confirmed "workflow column" and open the drop-down. {F112} Now select "Batch edit Tasks.." Check the list on top, to make sure you have the issues in you want. Now adjust the actions list like this: {F116} Change Status: in queue (Game) Now hit "Update Tasks" Herald will see the task, pick it up, and adjust workflows accordingly. You do not have to care about other settings in the issue. 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 } {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) in the Coloumn "New / Unconfirmed" {F102} 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} == Missing anything? Read the Feedback section. = Confirm an Issue Ready for ingame testing? Get a predictable game-state and start picking up an issue from "Open / Validated". ==== Claim it {F104} Open one or two issues in a second tab (usually ctrl + click). {F98} Select "Reassign / Claim" on the new input screen (red arrow). Add yourself in the "Assigned to" (green arrow) field. A comment is optional. ==== Test it Get in the latest dev-build and start with the supplied steps to reproduce the issue. == Confirmed Issue happens as described ==== Update workflow Drag it from "Open" to "Confirmed / Validated" {F108} ==== Add the result When you were testing a single issue or needed to adjust something to make it happen, its easiest to add your outcome directly {F106} Now update/add the testing results {F110} Make sure you have the correct build in the field. Type only the version number in the last tested version field, nothing else. Also add you and the people that tested together with you in the "assigned tester" field. ==== Send them to development In case you confirmed more than one issue in your testing run and they all were happening exactly as described, you can confirm them in one pass. If you do not own all tasks in that column, filter the others {F114} and go to the confirmed "workflow column" and open the drop-down. {F112} Now select "Batch edit Tasks.." Check the list on top, to make sure you have the issues in you want. Now adjust the actions list like this: {F116} Change Status: in queue (Game) Now hit "Update Tasks" Herald will see the task, pick it up, and adjust workflows accordingly. You do not have to care about other settings in the issue. == Failed to reproduce Issue happens as described = Feedback 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 yourself in the "Assigned to" (green arrow) field. Add a comment requesting for details and what details you need, now hit 'Submit'.