I am trying to add a new string field (IterationCompleted) to the bug work item in tfs2010. Using the TFS 2010 power tools I edited the work item adding the new field. This results in the following XML I added it to the form next to some related fields. Here is the relevant XML It is not involved in the workflow at all. The problem I'm having is in the form.

View TFS/VSTS Queries. Access and view project queries and work items directly in Outlook using filters and custom work item field mapping. Rapid Work Item Management. Create new or edit existing Team Foundation Server or Visual Studio Team Services work items in a built-in Outlook grid. Data types supported by work item fields to support queries, reports, and workflow for Visual Studio Team Services (VSTS) and TFS.

For new bugs, the field appears as expected and is editable (Iteration Resolved): For old bugs however, the field is not editable. In fact there is no control at all there to input anything: I found a with an accepted answer to make sure the field is String and that on the Form the type is set to FieldControl. As you can see I have done that and still get the results I am seeing above. I have successfully added fields in the past and never encountered this problem.

Does anyone know what I can do to get this field editable in old bugs? Cara Instal John The Ripper Untuk Windows 7. I just had this problem in TFS 2010 using VS2012.

Steps to reproduce: • Create custom field type:String • Add field to layout, ensure it is a FieldControl • Preview Form: Works fine • Go to a query and double click and existing work item of the type you are editing (for me it was a Backlog Item.) Observe no proper way to edit field, even if cursor shows in field. Open Media Wifi Bridge Software Design. Appears to be read only. After verifying the field was not read only (Property false in layout), I restarted Visual Studio after saving the edits. That cleared the issue and the edit control started working normally.

I can reproduce this over and over. I came across the same behaviour. Or at least similar. I had to add default values for all the lists. When I did not have a default value, any WIT's which had already been created could not have there values set, as it was not a ALLOWEDVAULES LISTITEM.

(Note: This code/XML changes the value of a list depending on the state of the WIT) Sample: End of Sample.