arauner
arauner

Reputation: 1

Team Foundation Server Using Custom Fields instead of System Fields

I'm introducing TFS 2010 in our company. After a lot of work on item customizations, I'm considering using custom fields as some system fields.

One example...

I've got some management requirements for the field "System.priority". This field should be set to "REQUIRED", so everyone has to do an estimation about the priority of a bug or task.

Are there any well known problems with creating an custom mypriority field and using it? (except the whole customizing afterwards for the basic reports...) I know i cant delete the system fields but i can delete the references for system.priority from the layout tab and then im going to use my own customized ones ..

Is this possible?

Upvotes: 0

Views: 392

Answers (1)

KMoraz
KMoraz

Reputation: 14164

Avoid creating custom fields when the default ones can serve the purpose. E.g.: Use the REQUIRED rule where needed:

<FIELD name="Priority" refname="Microsoft.VSTS.Common.Priority" type="Integer" reportable="dimension">
  <REQUIRED />    
</FIELD>

Upvotes: 1

Related Questions