<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workitems on Hermit Blog</title><link>https://hermit.no/categories/workitems/</link><description>Recent content in Workitems on Hermit Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 14 Dec 2008 16:06:34 +0100</lastBuildDate><atom:link href="https://hermit.no/categories/workitems/index.xml" rel="self" type="application/rss+xml"/><item><title>TFS Workitems : On the fields, their namespaces and in which workitem types they are used</title><link>https://hermit.no/archive/2008-12-14-tfs-workitems-on-the-fields-their-namespaces-and-in-which-workitem-types-they-are-used/</link><pubDate>Sun, 14 Dec 2008 16:06:34 +0100</pubDate><guid>https://hermit.no/archive/2008-12-14-tfs-workitems-on-the-fields-their-namespaces-and-in-which-workitem-types-they-are-used/</guid><description>&lt;p&gt;At the moment there are five different popular process templates, three from Microsoft official, one on Codeplex (by some Microsoft guys afaik), and one from &lt;a href="http://scrumforteamsystem.com/en/default.aspx"&gt;Conchango&lt;/a&gt;.  The fields defined in the workitemtypes found in these templates belongs to a set of namespaces.  The System namespace is a predefined Microsoft namespace, with special behavior.  The other ones are in reality free text.  However, since some effort has been placed on defining these namespaces, and some of these fields are used in several reports, in mappings to Microsoft Project etc., it is wise to adhere to these definitions. It will at least reduce the work you have to do if you&amp;rsquo;re modifying them, or defining your own types.  It is also wise to keep the fields named as equally as possible between types, and even processes, because it also simplifies querying across types. See &lt;a href="http://teamfoundation.blogspot.com/2008/05/work-item-customization-tidbits-part-1.html"&gt;http://teamfoundation.blogspot.com/2008/05/work-item-customization-tidbits-part-1.html&lt;/a&gt; for a great tutorial on how-to-do-it.&lt;/p&gt;</description></item><item><title>TFS Workitems : On the fields, their namespaces and in which workitem types they are used</title><link>https://hermit.no/posts/2008-12-14-tfs-workitems-on-the-fields-their-namespaces-and-in-which-workitem-types-they-are-used/</link><pubDate>Sun, 14 Dec 2008 16:06:34 +0100</pubDate><guid>https://hermit.no/posts/2008-12-14-tfs-workitems-on-the-fields-their-namespaces-and-in-which-workitem-types-they-are-used/</guid><description>&lt;p&gt;At the moment there are five different popular process templates, three from Microsoft official, one on Codeplex (by some Microsoft guys afaik), and one from &lt;a href="http://scrumforteamsystem.com/en/default.aspx"&gt;Conchango&lt;/a&gt;.  The fields defined in the workitemtypes found in these templates belongs to a set of namespaces.  The System namespace is a predefined Microsoft namespace, with special behavior.  The other ones are in reality free text.  However, since some effort has been placed on defining these namespaces, and some of these fields are used in several reports, in mappings to Microsoft Project etc., it is wise to adhere to these definitions. It will at least reduce the work you have to do if you&amp;rsquo;re modifying them, or defining your own types.  It is also wise to keep the fields named as equally as possible between types, and even processes, because it also simplifies querying across types. See &lt;a href="http://teamfoundation.blogspot.com/2008/05/work-item-customization-tidbits-part-1.html"&gt;http://teamfoundation.blogspot.com/2008/05/work-item-customization-tidbits-part-1.html&lt;/a&gt; for a great tutorial on how-to-do-it.&lt;/p&gt;</description></item></channel></rss>