Task States and Transitions
A task is a work item that communicates the need to do some work. Each role has its own requirements for a task. For example, a developer uses development tasks to assign work derived from scenarios or quality of service requirements to component owners. The tester uses test tasks to assign the job of writing and running test cases. A task can also be used to signal regressions or to suggest that exploratory testing be performed. Finally, a task can be used generically to assign work within the project.
New
A new task work item can be created whenever new work is identified that needs to be done. Tasks are generally created as the result of analysis of other work items such as issues and requirements.
New to Proposed
|
New |
A task is proposed as a new task when it is first created. |
Proposed
Proposed tasks represent work upon which agreement to do has not yet been reached. Proposed tasks are triaged and either accepted or rejected during the triage process.
Proposed to Active
|
Accepted |
A task is activated as Accepted when it is reviewed in triage and the determination is made that the work represented by the task is appropriate for the current iteration. |
Proposed to Closed
|
Rejected |
A task is closed as Rejected when it is reviewed in triage and the determination is made that the work represented by the task is inappropriate due to some factor such as missing information or an incorrect analysis. |
Active
An active task indicates there is some element of work to be done. All active tasks should be assigned to an owner.
Active to Resolved
|
Complete Requires Review/Test |
A task is resolved as Complete Requires Review/Test when the work represented by the task, such as developing code, or writing documentation, is complete and now requires review through testing or peer reviews. |
Active to Closed
|
Deferred |
A task is closed as Deferred if it cannot be implemented in the current iteration. A task could be deferred because the team does not have enough time, or because blocking issues were discovered. Update the Iteration field to the correct iteration in which the task will be implemented. |
|
Cut |
A task is closed as Cut if the original work item, such as a requirement or issue, is closed and not to be worked on. |
|
Cancelled |
A task is closed as Cancelled if the work it represents is no longer applicable to completion of the product. |
|
Overtaken by Events |
A task is closed as Overtaken by Events when something has happened that obviates the need for the task. Typically an untracked activity that accomplishes the same work as the task causes this to happen. |
|
Complete and Does Not Require Review/Test |
If a task does not require review or test, it can simply be Closed without the need to resolve it. |
Resolved
A resolved task is completed. The output from the task must be reviewed or tested, and if acceptable, the issue will be closed. If the output is not acceptable, the task will return to an Active state for further work.
Resolved to Active
|
Review/Test Failed |
A task is reactivated as Review/Test Failed if the review or test fails for the output of the task. |
Resolved to Closed
|
Review/Test Passed |
A task is closed as Review/Test Passed if the review or test passes for the output of the task. |
Closed
A closed task means that no further work is to be done for the current product version. A development task is closed after the code changes have been integrated. A test task is closed when all of the tests are complete for that area.
Closed to Active
|
Closed in Error |
A task is reactivated if a mistake was made and it should not have been closed yet. |
|
Reactivated |
A task is reactivated if it was deferred in a previous iteration and can now be completed in the current iteration. | | 
