816
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − + Line 18:
Line 18: − + Line 25:
Line 25: − + − + Line 34:
Line 34: − + Line 42:
Line 42: − + − + Line 60:
Line 60: − +
Robot: Automated text replacement (-QATeam +TestingTeam)
{{TeamHeader|QATeam}}
{{TeamHeader|TestingTeam}}
= Bugsquad Triage Guide =
= Bugsquad Triage Guide =
=== Read the Stock Responses ===
=== Read the Stock Responses ===
The [[QATeam/TriageGuide/StockResponses]] are general examples of the kinds of comments that triagers should add to bug reports. Please read them carefully. In most cases you can use one of them as a comment.
The [[TestingTeam/TriageGuide/StockResponses]] are general examples of the kinds of comments that triagers should add to bug reports. Please read them carefully. In most cases you can use one of them as a comment.
== Triaging ==
== Triaging ==
=== Find what should be changed===
=== Find what should be changed===
Read the [[QATeam/TriageGuide#Steps_of_Triaging]] to determine what should be changed (if anything) and how.
Read the [[TestingTeam/TriageGuide#Steps_of_Triaging]] to determine what should be changed (if anything) and how.
=== Ask someone to verify your changes ===
=== Ask someone to verify your changes ===
For the first bugs we encourage you to make the changes in conjunction with a member of the bugsqad team [[QATeam/Contacts#List_of_Triagers]]. You will find them usually at #sugar on freenode.
For the first bugs we encourage you to make the changes in conjunction with a member of the bugsqad team [[TestingTeam/Contacts#List_of_Triagers]]. You will find them usually at #sugar on freenode.
=== Make your changes ===
=== Make your changes ===
== Steps of Triaging ==
== Steps of Triaging ==
These are some notes how to triage the bugs in detail. In all the cases you can find the matching stock response at [[QATeam/TriageGuide/StockResponses]].
These are some notes how to triage the bugs in detail. In all the cases you can find the matching stock response at [[TestingTeam/TriageGuide/StockResponses]].
=== Verify that the bug is not a duplicate ===
=== Verify that the bug is not a duplicate ===
=== The bug report need some logs ===
=== The bug report need some logs ===
In most of the cases the developer could use some logs to better identify the problem. Instructions on how to take logs are at [[QATeam/GetLogs]].
In most of the cases the developer could use some logs to better identify the problem. Instructions on how to take logs are at [[TestingTeam/GetLogs]].
=== If the bug is not described well ===
=== If the bug is not described well ===
The bug report isn't very useful if the bug isn't described well. Some people do not read the [[QATeam/BugHowto]] or are just inexperienced. Best, is to use one of the stock answers and go to the next bug :)
The bug report isn't very useful if the bug isn't described well. Some people do not read the [[TestingTeam/BugHowto]] or are just inexperienced. Best, is to use one of the stock answers and go to the next bug :)
=== If the bug is in an obsolete version of the application ===
=== If the bug is in an obsolete version of the application ===
[[Category:QATeam]]
[[Category:TestingTeam]]