Answered by:
Can IterationPath be made a required field?

Question
-
I am trying to make the System.IterationPath field force the user to select an item in the list that is not the root item. When a new work item is created the iteration path is defaulting to the root node and I need the user to select one of the version numbers from the list.
So using the process editor I added xml as follows.
<FieldDefinition type="TreePath" name="Iteration Path" refname="System.IterationPath">
<HELPTEXT>The iteration of the product with which this change request is associated</HELPTEXT>
<PROHIBITEDVALUES>
<LISTITEM value="RootValue" />
</PROHIBITEDVALUES>
</FieldDefinition>But when I try to save the work item type the editor gives the error...
There were validation errors. Continuing to save may cause the file to become unloadable, do you want to continue?
Work Item Type "MyWorkItemType":
TF26062: Rule '<PROHIBITEDVALUES></PROHIBITEDVALUES>' is not supported for the field 'System.IterationPath'.Is there any other way to achieve this behavior?
Thanks
-- Steven
Monday, April 7, 2008 8:27 PM
Answers
-
Unfortunately, this is not possible - we do not support rules for tree node fields.
Alex
Monday, April 7, 2008 9:02 PMModerator -
Thanks Steve. This feature is on *my* wish list for Rosario. I've placed it in the category of adding rules to Iteration and Area Path fields. Rules like REQUIRED, ALLOWEDVALUES, DEFAULT, and MATCH would meet a lot of requirements, including the one you are presenting.
I feel your pain. I wish I could say: "It will be in Rosario", but I can't. Its on the backlog, however.
Wednesday, April 23, 2008 4:52 PMModerator
All replies
-
Unfortunately, this is not possible - we do not support rules for tree node fields.
Alex
Monday, April 7, 2008 9:02 PMModerator -
Thanks for the quick reply Alex.
Thats unfortunate, any chance this could be put on the wish list for Rosario?
-- Steven
Monday, April 7, 2008 9:41 PM -
Steven, I have forwarded your question to our PM team; you should hear from them shortly.
Thanks,
Alex
Monday, April 7, 2008 9:43 PMModerator -
Thanks Steve. This feature is on *my* wish list for Rosario. I've placed it in the category of adding rules to Iteration and Area Path fields. Rules like REQUIRED, ALLOWEDVALUES, DEFAULT, and MATCH would meet a lot of requirements, including the one you are presenting.
I feel your pain. I wish I could say: "It will be in Rosario", but I can't. Its on the backlog, however.
Wednesday, April 23, 2008 4:52 PMModerator -
Did this flexibility make it into TFS 2010?
Best Regards, David K Allen http://codecontracts.info Minneapolis, Minnesota, USAThursday, March 18, 2010 3:17 AM -
I'm still getting a similar error in TFS 2010 although I'm trying to set a default rule instead of a prohibited values list like the original poster, so it seems not.
Would love to know if it's possible to set a default value for the iteration path field for a work item type in TFS 2010.
Sunday, June 13, 2010 1:40 PM