3 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Visual Studio ALM Team commented  ·  October 27, 2011 10:20 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Glad you found the blog post on this. Being able to add rules on these fields (Area and Iteration) is on our backlog. We are adding functionality in the vNext release which will default these fields based on what team you are a member of. Each team can define default values for these fields, and by working in the context of a team, these values are then defaulted when creating new work items. We hope this addresses a lot of the need for rules on these fields.

  Gregg Boer - MSFT / TFS Product Group

• Neno commented  ·  August 15, 2011 4:02 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Exactly, the <REQUIRED> rule (or a new rule) should make sure an area node is selected, which is not the root area.

• Anonymous commented  ·  August 9, 2011 3:14 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is not so easily, because these fields are allready required (allways filled with data) so there is a need for different mechanisms. And there is a mechanism also for Area/Iteration path fields. We are using this for some projects since TFS 2008 times.
  http://blogs.msdn.com/b/teams_wit_tools/archive/2009/02/07/work-item-rules-workarounds-validating-area-path.aspx