RR Status Transition Process

By default, the life cycle of an RR consists of the Analyzing, Confirm, Planning, Implementing, Delivering, Accepting, and Closed states. Figure 1 shows the complete status transition process.

Figure 1 RR status transition flowchart

Table 1 lists the default operations in each RR state.

**Table 1** Operation description
State	Description
--	When you create an RR, the status is -- by default after you save it as a draft. The requirement proposer is by default the person who creates the requirement.
Analyzing	After the RR is submitted, the state changes to Analyzing. The requirement recipient can analyze whether to accept the requirement based on the requirement content. If not, the requirement can be returned or suspended. After the requirement is returned, the state changes to Confirming. The requirement proposer can directly cancel the requirement or submit the requirement again.
Planning	After the RR is accepted, the state changes to Planning. The requirement recipient makes development plan on the requirement. If the requirement does not involve R&D, select R&D not required, and the state of the requirement changes to Accepting.
Implementing	After the R&D of the RR starts, the state changes to Implementing. If there is any problem with the implementation solution, the requirement recipient can return the requirement to the planning phase.
Delivering	After the R&D of the RR is completed, the state changes to Delivering. If the delivery cannot meet the expectation, the requirement recipient can return the requirement to the planning or implementing phase.
Accepting	After the RR is submitted for acceptance, the state changes to Accepting. The requirement proposer checks whether the content of the requirement meets acceptance conditions. If not, select Acceptance failed and the state of the requirement goes back to Delivering.
Closed	After the RR is accepted, the state changes to Closed.