Process Configuration XML Element Reference

AddPanel

Container element used to specify the “quick add” experience, the fields to appear within the panel area where new backlog items are defined.

<AddPanel>
    <Fields>
       <Field . . . />
       . . .
   </Fields>
</AddPanel>

Required. One instance only.

You must specify at least one Fields element.

The “quick add” experience only appears on the Product Backlog page in Team Web Access.

Columns

Specifies a collection of Column elements.

<Columns>
   <Column . . . />
   . . .
</Columns>

Required. One instance only for each IterationBacklog and ProductBacklog parent elements.

You must specify the columns that you want to appear on the pages that display the product backlog or an iteration backlog.

Fields

Specifies a collection of Field elements.

<Fields>
<Field . . . />
   . . .
</Fields>

Required. One instance only defined for the AddPanel parent element.

You specify the fields that you want to specify quickly when adding items to the product backlog.

ProductBacklog

Container element used to customize the layout of the page that displays the product backlog and that contains a panel for adding work items to the backlog.

<ProductBacklog>
   <Columns> . . . </Columns>
   <AddPanel> . . . </ AddPanel>
</ProductBacklog >

Required. One instance only.

You specify the number of columns, column widths, and the fields that populate each column for those pages that display the list of backlog items assigned to the product backlog. The product backlog displays all active items in the backlog, including those that have been assigned to an iteration.

BugWorkItems

Required. Specifies the category that corresponds to bug work items and associates the workflow states of backlog items with metastates. The CategoryName must correspond to a category defined for the team project.

<BugWorkItems category=”CategoryName”>
    <States>
       <State . . . />
       . . .
   </States>
</BugWorkItems

FeedbackResponseWorkItems

Required. Do not customize.

Specifies the category that corresponds to work item types that are used to capture feedback response and associates the workflow states of these items with metastates. The CategoryName must correspond to a category group defined for the team project.

<FeedbackResponseWorkItems category="Microsoft.FeedbackResponseCategory" plural="Feedback Responses">
   <States>
      <State value="Active" type="InProgress" />
      <State value="Closed" type="Complete" />
   </States>
</FeedbackResponseWorkItems>

RequirementWorkItems

Required. Specifies the category that corresponds to backlog items, such as user stories, requirements, and product backlog items and associates the workflow states of backlog items with metastates. The CategoryName must correspond to a category group defined for the team project. Specify category groups using the Categories.xml file.

<RequirementWorkItems category="CategoryName" plural="NameOfBacklogItems" >
   <States>
      <State . . . />
      . . .
   </States>
</RequirementWorkItems>

States

Required element for the BugWorkItems, FeedbackResponseWorkItems, FeedbackRequestWorkItems, RequirementWorkItems and TaskWorkItems elements.

Specifies a collection of State elements that associate the workflow states of types of work items with metastates.

<States>
   <State . . . />
   . . .
</States>

State elements are used to assign workflow states to metastates.

TypeField

Required. Specifies the reference name of a field whose value is referenced to support a type of activity for a supported feature area. You specify this element within the TypeFields container element. You must specify the fields that correspond to the fields that you use within the types of work items to capture specific information.

<TypeField refname=”FieldReferenceName” type=”NameOfType” [format="{0} TimeUnitString"] / >

Specifying the format is only valid when type="RemainingWork". You can specify any text string for the TimeUnitString that you want to have appear on the capacity bars on the current iteration backlog page and on the task board.

For the backlog and task board pages:

• Activity: Used to support the capacity-by-activity feature. Specify a field defined for the task type of work item that you use to specify the type of activity to be performed.

• Effort: Specifies the field used to calculate the team velocity. Specify a field defined for the backlog type of work item that you use to capture the level of effort or the relative rating for the amount of work that a backlog item will require to implement.

• Order: Specifies the field used to define the sort order for backlog items on the iteration backlog and task board pages. Specify the field that you use to capture the relative priority assigned to backlog items. Work items are listed on the page according to the ascending order as defined by the field for this type.

• RemainingWork: Specifies the field used to calculate remaining work and burndown charts. Specify the field that you use to capture the number of hours or days that remain to finish a task.

  The value that you specify for format is used on the backlog and task board pages wherever remaining work is reported. For example, when reporting capacity-by-activity or capacity per team member, or next to the column heading for the task states on the task board.

  For TimeUnitString, specify any text string that you want to use to reflect the time value, such as hours or days.

  For example, the following values are all valid:

  format="{0} h"

  format="{0} hours"

  format="hours {0}"

  format="time {0}"

• Team: Specifies the field used to associate the backlog and task board pages with a team. The default value is System.AreaPath. To decouple teams from area paths, you can specify a different field, as described in Customize a team project to support team fields.

For the feedback request form:

• ApplicationStartInformation: Specifies the field used to capture the path to execute the application.

• ApplicationLaunchInstructions: Specifies the field used to capture launch instructions.

• ApplicationType: Specifies the field used to capture the type of application. The types listed correspond to the allowed values specified in the type definition for the feedback request.

TypeFieldValue

Required. Do not customize.

Specifies the name of an application type to appear on the feedback request form.

<TypeFieldValue value="ApplicationTypeName" type="TypeApp"/>

The default assignments correspond to the allowed values specified in the type definition for the feedback request form.

<TypeFieldValues>
   <TypeFieldValue value="Web application" type="WebApp" />
   <TypeFieldValue value="Remote machine" type="RemoteMachine" />
   <TypeFieldValue value="Client application" type="ClientApp" />
</TypeFieldValues>

Weekends

Optional. Container element used to specify non-working days.

<Weekends>
   <DayOfWeek> . . . </DayOfWeek >
   . . . 
</ Weekends >

Specify non-working days when you want to account for non-working days in the calculation of capacity and burndown charts.