Asked by:
How to change upper/lower case in a TFS work item field definition (WIT)?

-
I have a weird problem with the configuration of TFS 2010 work items. It seems to be impossible to change the case of characters in the allowed values collection of a field e.g. change "Works for me" to "Works For Me". Every other string e.g. "Works For Me 123" is valid.
Even if I try to change the name to another string first (since i know the similar case problem with files in Visual Studio projects) it is just not accepting the upper case version and returns always to the lower case string.
Background information:
We have a custom WIT file to define the "Bug" work item. This includes the definition of the allowed values for the field "Resolved Reason". Initially our list contained lower case words e.g. "Works for me". Since we want to synchronize the TFS work items with HP Quality Center we need an exact match of the state names now.
The desired version:
<FIELD name="Resolved Reason" refname="Microsoft.VSTS.Common.ResolvedReason" type="String" reportable="dimension"> <HELPTEXT>The reason why the bug was resolved</HELPTEXT> <ALLOWEDVALUES expanditems="true"> <LISTITEM value="Duplicate" /> <LISTITEM value="Fixed" /> <LISTITEM value="Wont Fix" /> <LISTITEM value="Invalid" /> <LISTITEM value="Works For Me" /> <LISTITEM value="Forwarded" /> </ALLOWEDVALUES> </FIELD>
The actual version:
<FieldDefinition reportable="dimension" refname="Microsoft.VSTS.Common.ResolvedReason" name="Resolved Reason" type="String"> <ALLOWEDVALUES> <LISTITEM value="Duplicate" /> <LISTITEM value="Fixed" /> <LISTITEM value="Wont fix" /> <LISTITEM value="Invalid" /> <LISTITEM value="Works for me" /> <LISTITEM value="Forwarded" /> </ALLOWEDVALUES> <HELPTEXT>The reason why the bug was resolved</HELPTEXT> </FieldDefinition>
Any ideas are welcome.
Thanks, Robert
Wednesday, February 23, 2011 2:50 PM
Question
All replies
-
Sounds like the values may be cached...try running this from the Visual Studio Command Prompt:
witadmin rebuildcache /collection: http://servername:8080/tfs/Collection0
Esteban Garcia - My blogWednesday, February 23, 2011 3:04 PM -
Hi Robert,
Does EstebanFG's suggestion work?
Best Regards,
Cathy Kong [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Friday, February 25, 2011 8:14 AMModerator -
Unfortunately not. I assume witadmin is only rebuilding the client cache, but the problem is somewhere on the server.
Regards,
Robert Hahn
Friday, February 25, 2011 10:26 AM -
Hi Robert,
Sorry for the delayed response!
I cannot repro this issue, I would suggest you to report this issue on our Connect Portal:
https://connect.microsoft.com/VisualStudio/
Every feedback submitted will be evaluated carefully by our engineers. If they have some feedback on it, they will let us know their comments further through that portal. This would be helpful to improve Visual Studio products.
Cathy Kong [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Monday, March 07, 2011 9:38 AMModerator -
The values are case insensitive. I had a similar issue as well. Vote on the idea below if you want MSFT to fix it!
Monday, March 07, 2011 2:57 PM -
The values are case insensitive. I had a similar issue as well. Vote on the idea below if you want MSFT to fix it!
I have a client experiencing the same problem; Was anyone able to find a work around?
Tuesday, November 19, 2013 3:41 PM -
I have this problem also. Does anyone have a workaround of this problem????Wednesday, June 11, 2014 12:09 PM