Page MenuHomeSchine - Phabricator

Issue Navigation
Updated 3,254 Days AgoPublic

Version 4 of 16: You are viewing an older version of this document, as it appeared on Jun 3 2015, 9:50 PM.

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?

now click on the box showing "Workflow Issue Navigation"

Now, you should see the "Issue Navigation Workboard"

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.

And open the issue by clicking the title.

Scroll to the end and

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.

Confirm an Issue

Ready for ingame testing?
Get a predictable game-state and start picking up an issue from "Open / Validated".

Last Author
AndyP
Last Edited
Jun 3 2015, 9:50 PM

Document Hierarchy

Event Timeline

AndyP created this document.May 31 2015, 11:44 PM
AndyP edited the content of this document. (Show Details)
AndyP edited the content of this document. (Show Details)Jun 1 2015, 10:38 PM
AndyP edited the content of this document. (Show Details)Jun 3 2015, 9:35 PM
AndyP edited the content of this document. (Show Details)Jun 3 2015, 9:50 PM
AndyP edited the content of this document. (Show Details)Jun 3 2015, 9:53 PM
AndyP edited the content of this document. (Show Details)Jun 3 2015, 9:55 PM
AndyP edited the content of this document. (Show Details)Jun 4 2015, 7:20 AM
AndyP edited the content of this document. (Show Details)Jun 4 2015, 8:04 AM
AndyP edited the content of this document. (Show Details)
AndyP edited the content of this document. (Show Details)
AndyP edited the content of this document. (Show Details)Jun 4 2015, 9:10 AM
AndyP edited the content of this document. (Show Details)
AndyP edited the content of this document. (Show Details)Jun 5 2015, 12:24 AM
AndyP edited the content of this document. (Show Details)Jun 5 2015, 12:41 AM
AndyP edited the content of this document. (Show Details)
AndyP edited the content of this document. (Show Details)Jun 27 2015, 3:58 PM