Confirmed users
2,177
edits
TestEngineering/Performance/Triage Process: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Triage Process (view source)
Revision as of 17:31, 10 February 2020
, 10 February 2020no edit summary
(Added link to triage meeting document) |
No edit summary |
||
| Line 1: | Line 1: | ||
Workflow | == Workflow == | ||
* Triage incoming bugs as early as possible. To be able to do that there should be at least one person who is watching the component for all changes. The triage team decides who is responsible for that task until the next triage meeting. | * Triage incoming bugs as early as possible. To be able to do that there should be at least one person who is watching the component for all changes. The triage team decides who is responsible for that task until the next triage meeting. | ||
| Line 10: | Line 10: | ||
* When you stop working on a bug or when it is blocked by another one, reset the priority to its original value, and unassign yourself. | * When you stop working on a bug or when it is blocked by another one, reset the priority to its original value, and unassign yourself. | ||
Priorities | == Priorities == | ||
* P1 - This bug represents an OKR, and has an assignee working on an implementation | * P1 - This bug represents an OKR, and has an assignee working on an implementation | ||