This post is the fifth and last post out of Five that builds the Work Items Basic Guide. See the first post: “Team System Work items Basic User Guide – Introduction”
I have already published the “Team System Work Items Basic User Guide – Create New Work Items”, the “Team System Work Items Basic User Guide – Create And Use Queries” and the “Team System Work Items Basic User Guide – Create New Work Items Out Of An Existing Work Items”
We have seen in previous posts how to create a new work item we have seen how to create and manage my queries and how to create a new Work Item out of an existing Work Item on this post we will see what are the Core Fields of the work item.
Note: This post is for more advanced users or for curios users.
Work Item Types can be deferent from one another, each can have a different Fields, Look and Work Flow but there are a few fields that are the same for all Work Item Types, they are called Core Fields.
What are Core Fields?
Core Fields contains information that influence the operation of the system or influence the process.
Not all Core Fields are required for all Work Item types and some are filled automatically in the background.
The list of the Core Fields are:
- TeamProject – This is the Team Project name that the work item belongs to.
This field is filled automatically by the system.
- WorkItemType – The Type of the work item.
This field is filled automatically by the system.
- Id – The ID of the Work Item in the server, the ID of the work item is unique for the TFS and not for a project.
This field is filled automatically by the system.
- AreaId and AreaPath – These two fields represents the Product Tree. (I will explain what is a Product Tree and how to create it in a future post)
These fields have a default value that the user can control and change.
- IterationId and IterationPath - These two fields represents the Process Tree. (I will explain what is a Process Tree and how to create it in a future post)
These fields have a default value that the user can control and change.
- State and Reason – These two fields represents the Work Flow of the Work Item Type, the State shows the current state of the work item and the Reason shows why we got to the current state.
These fields have a default value that the user can control and change, the values shown in the fields are according to the Work Flow of the Work Item Type.
- AssignedTo – This shows the user responsible of the Work Item, for each State there can be different users responsible.
- History and Rev – These two fields are keeping the history and revision of the Work Item, each change made for the Work Item is digitally signed and shown in the History field.
These fields are filled automatically by the system, the user can only add comments to a revision.
- Title – This field is the title of the Work Item, it is not a required field.
- Description – This field is the description of the Work Item, it is not a required field.
- ChangedBy and ChangedDate – These fields are for tracking changes.
These fields are filled automatically by the system.
- CreatedBy and CreatedDate – These fields are for tracking the creator and the date the Work Item was created.
These fields are filled automatically by the system.
- RevisedDate – This field is for the History and Rev fields use.
This field is filled automatically by the system.
- AttachedFileCount, ExternalLinkCount, RelatedLinkCount and HiperLinkCount – These fields are counters for links and attachments.
These fields are filled automatically by the system.
- AuthorizedAs – used to store the name of the user who is authenticated to make the change
- NodeName – Gets the Node Name of the Work Item.
This field is filled automatically by the system.
Most chances that you will not see most of the fields in the form's layout, most of the listed fields are used in the background and for reports.
Have Fun!!!