Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| Task
### Work Item Database
Overview |
States and Transitions |
Fields |
### Process Guidance |
Activities |
Workstreams |
Task Fields 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.
Field | Description
--- | ---
Title | Required. The title provides a concise overview of the task to be completed. The title should be descriptive enough to allow the team to understand what area of the product is affected and how it is affected.
Type | Indicates whether the task is a development task, test task, analysis task, user experience task (Ux), or user education task (Ue). Setting the Type field determines the meaning about the state of the work when the task is closed. It also helps when querying for tasks assigned to certain areas, such as finding all test related tasks. Valid values are Analysis, Ux, Ue, Development, or Test.
Area Path | Used to group the task into an appropriate feature or team area. The area path must be a valid node in the project hierarchy.
Iteration Path | The scheduled iteration in which the task is carried out.
Assigned To | The current person that the task is assigned to.
State | Required. A task can be in the Proposed, Active, Resolved, or Closed states.
Reason | Required. The reason a task is in the current state. For example, the task may be closed because it is Deferred.
Priority | Required. The priority field is a subjective importance rating used to determine which tasks to complete first. Valid values are 1, 2, and 3.
Description | Details about the task describing what exactly needs to be done.
Attachments | Contains attached files to provide more information on the task such as notes.
Estimate | The amount of estimated work in person hours that remain to finish the task. Ideally this amount should not exceed 120 hours; such tasks should be divided into smaller tasks.
ID | The unique identifier used to identify the task. Team Foundation Server automatically creates the ID when the work item is created.
History | Describes what activity has occurred each time the task is updated with new information. This field is a running history of activity on the task.
Requires Review | Indicates if the task requires a review to verify that it is completed correctly. This field is a value of Yes or No.
Requires Test | Indicates if the task requires a test to verify that it is completed correctly. This field is a value of Yes or No.
Created By | Identifies who created the task.
Created Date | Identifies when the task was created.
Changed By | Identifies the person who last made a change to the task.
Changed Date | Identifies the date the task was last changed.
Closed By | Identifies the person who closed the task.
Closed Date | Identifies the date the task was closed.
Remaining Work | This field records how much time is left to complete the task in person hours.
Completed Work | This field records how much time has been spent on the task in person hours.
Integrated In | Identifies the build that contains the changes made that comprise the task.
Blocked | Indicates if progress on completing the task has been blocked. If an Issue work item has been opened to track the blocking problem, a link should be made to that work item as well.
Triage | This field is used during the Proposed state. It provides sub-states for a task awaiting a triage decision. Valid values are Pending (default), More Info, Info Received, Triaged.
Links | This field shows the other work items that have been linked to the task. In the case of a development or test task, the supporting scenario or quality of service requirement should be linked.
Test Name | Indicates the name of the test that was run on the task code. This appears as Name on the Test tab.
Test ID | Indicates the ID number of the test that was run on the task code. This appears as ID on the Test tab.
Test Path | Indicates the path of the test that was run on the task code. This appears as Path on the Test tab.
Resolved By | Identifies who resolved the task. This information appears in the History field and not in its own field.
Resolved Date | Identifies when the task was resolved. This information appears in the History field and not in its own field.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |