Introduction to Status Transition

The entire lifecycle of a defect has five states: Analyzing, Fixing, Testing, Accepting, and Closed.

Table 1 describes operations in each state.

**Table 1** Operation description
State	Description	Operation
-	Creating bugs By default, the bug proposer is the person who finds the bug.	Creating Bugs
Analyzing	After the bug is submitted, the state changes to Analyzing. The current owner analyzes the bug as follows: If the analysis result shows that the bug is not a problem, click Fixing not required to transfer the bug to the proposer. If the description is incorrect, click Return To to transfer the bug to the current owner for modification. After the analysis is complete, click Submit to R&D.	Analyzing Bugs
Fixing	After the bug is analyzed, the state changes to Fixing. The current owner fixes the bug based on the problem.	Fixing Bugs
Testing	After the bug is fixed, the state changes to Testing. The current test owner verifies whether the problem is fixed based on the rectification result. If the result does not meet the expectation, the test owner can return it for fixing or analysis.	Testing Bugs
Accepting	After the bug is tested, the state changes to Accepting. The current acceptance owner tracks the verification result of the acceptance test.	Accepting Bugs
Closed	After the acceptance is passed, the state changes to Closed. A closed bug can be activated. After a bug being activated, its state will change to Analyzing.	-