Bug Status Transition Process

The entire lifecycle of a bug has five states: Analyzing, Fixing, Testing, Accepting, and Closed. Figure 1 shows the complete status transition process.

Figure 1 Bug status transition flowchart

Table 1 describes the operations in each status.

**Table 1** Operation description
Status	Description
--	Creating bugs By default, the bug proposer is the person who finds the bug.
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 Fix.
Fixing	After the bug is analyzed, the state changes to Fixing. The current owner fixes the bug based on the problem.
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.
Accepting	After the bug is tested, the state changes to Accepting. The current acceptance owner tracks the result of the acceptance test.
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.