The team that is associated with the project category that a Request references reviews the Request and determines if it can be addressed in the project. If the Request will be addressed, a Task is created and associated with the Request. Anyone looking at Request can see which Tasks are needed to fulfill it. Anyone looking at the Task can see which Request it is intended to complete.
In the primary flow for a Task, the Task starts in an Opened state. The Task record is moved to the Activated state when work is being done. When a resolution is accepted, the record is moved to a Completed state.
Typically, some lead role (which may be the same as the developer/project manager role), processes the workflow for a Task. In the basic work process, Activities that resolve the Task are created and then assigned.
The Task owner typically creates Activities that will complete the Task. The Task owner normally uses the CreateActivity action which creates a set of necessary Activities based on the WorkConfiguration record for the project. For example, the Activate action could automatically create a unique Activity for Development, for Testing, and for Documentation.