Showing posts with label field. Show all posts
Showing posts with label field. Show all posts

Sunday, 30 July 2017

Show Hidden Fields with Empty Values for Edit - Kanban Cards - Team Services

With the latest release to Team Services Kanban Card has been added with a new feature. Previously, if you want to edit a value in a field that is currently empty, in the Kanban Card You  had to keep it showing even if value is empty. With the new feature available now you can let Kanban Card to hide a field, if it is empty and expand the Card to show empty fields  so that you can edit them.

Thursday, 22 June 2017

Team Services Process Customization

Team Services is coming up with many improvements and one of it is the new process customization experience introduced recently. This allows you to have your own custom work item types, custom work item state flows and custom fields for work items etc. It is made easier to start customizing even directly from work item form. Let’s look at and understand process customization options available for you to optimize your work process.

Sunday, 27 October 2013

TFS - Delete WIT Custom Fields Permanently


When you delete a custom filed from a Work Item Template and import is it really deleted from TFS fully? Or is it only hidden from that work item type and remains in TFS?

To find out the answer I have done a small experiment.

1. Fist I have added a new HTML type filed "CH.Test1" and added a HTML field control to User Story work item.



2. When I have imported the template I can see my new field in User Story work item.


3. I saved some data to newly created field.


4. Then I deleted the HTML field control and the filed "CH.Test1" in the template.


5. When viewed the previous user story I could not see the field and that is correct and field is deleted.


6. But what happens if I add the field again? To Investigate I tried adding the field with Same Reference Name but with a different name.



7. Import failed with

Error importing work item type definition:

TF26177: The field CH.Test1 cannot be renamed from 'Chaminda Test 1' to 'Chaminda Deleted And Added Field'.


8. This means that the field was not really deleted. To test I changed to the initial name "Chaminda Test 1"


9. Import was successful and when I viewed the same user story data I had entered before deleting the field was still available. It looked clear that even if I deleted a field from WIT template and import it did not delete the field or the data from TFS Collection.


8. Search in MSDN got me here Manage work item fields [witadmin]
I used witadmin listfields with Reference Name to see my field. The command gave the details of the field, whether it was used, In which project it was used.


9. Again I tried deleting from template and import.


10. When I used witadmin listfields with Reference Name, it clearly showed field is existing in collection but "Not In Use" in any team project.


11. How to delete permanently? I used witadmin deletefield with Reference Name, this gave me a warning and a confirmation question. When said Yes deleted. To verify I executed witadmin listfields with Reference Name again and an error shown that the field does not exist.


12. To confirm I tried re-adding the field with same Reference Name but with a different Name, and a different data type (String).



13. This time I did not get TF26177 when the template was imported.


Conclusion: When a field is deleted from the work item template and imported it remains in TFS collection and previously entered data related to work item also preserved. To delete the field permanently witadmin deletefield can be used and all data and the field will be completely destroyed with this command.

Popular Posts