将字段和字段规则添加到FIELDS节。 要使字段显示在工作项窗体上,还必须将其添加到定义的 FORM节。 例如,若要将工作项 ID 添加到窗体,请在FORM节中指定以下 XML 语法。 XML复制 <ControlFieldName="System.ID"Type="FieldControl"Label="ID"LabelPosition="Left"/> ...
将字段和字段规则添加到 FIELDS 节。 要使字段显示在工作项窗体上,还必须将其添加到 定义的 FORM 节。例如,若要将工作项 ID 添加到窗体,请在 FORM 节中指定以下 XML 语法。XML 复制 <Control FieldName="System.ID" Type="FieldControl" Label="ID" LabelPosition="Left" /> 若要详细了解如何定义字段,...
项目包含 100 个或多个数据字段,具体取决于用于创建项目的过程,例如敏捷、基本、Scrum或CMMI。每个工作项都与工作项类型 (WIT) 相关联,可以跟踪的数据对应于分配给 WIT 的字段。 通过修改工作项中的数据字段来更新工作项的数据。 备注 对于Azure DevOps Services 或使用继承的进程模型的项目集合,请参阅向工作项类...
). All System fields are defined for all work item types, whether or not you include them in the work item type definition. To learn more about each field, see Work item field index.You add fields and field rules to the FIELDS section. For the field to appear on the work item form,...
<STATE value="Resolved"> <FIELDS> . . . <FIELD refname="Microsoft.VSTS.Common.ResolvedReason"> <COPY from="field" field="System.Reason"/> </FIELD> </FIELDS> </STATE> 相关文章工作流状态和状态类别 自定义工作跟踪体验 按分配、工作流或板更改进行查询 设计工作项窗体 导出、导入和管理工作项类型...
The following examples show some of the rules that are applied to system fields in the process template for MSF Agile Software Development. Change the value of a field when the state changes When the value of theStatefield for a work item is set to Active and the work item is saved, the...
System fields have System.Namereference names, for exampleSystem.TitleandSystem.State. The following system fields are required to have a value:Area ID,Changed Date,Created Date,Created By,State, andReason. The rule engine restricts setting conditions or actions to system fields except as follows:...
Note that op is a constant, and <key> is expected to be a valid field name under DevOps /fields enumeration.Here are a few usage examples. You can fine more examples in Work Items - Update REST API.History update key = System.History value = Moving to the right area path` Move ...
<TypeFields> <TypeField refname="System.AreaPath" type="Team" /> <TypeField refname="Microsoft.VSTS.Scheduling.RemainingWork" type="RemainingWork" format="format h" /> <TypeField refname=" Microsoft.VSTS.Common.BacklogPriority" type="Order" /> <TypeField refname="Microsoft.VSTS.Scheduling.Ef...
Note that op is a constant, and <key> is expected to be a valid field name under DevOps /fields enumeration.Here are a few usage examples. You can fine more examples in Work Items - Update REST API.History update key = System.History value = Moving to the right area path` Move ...