{"id":20935,"date":"2016-09-02T19:45:46","date_gmt":"2016-09-02T23:45:46","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/?p=20935"},"modified":"2019-02-14T15:56:22","modified_gmt":"2019-02-14T23:56:22","slug":"custom-work-item-types-on-team-services","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/custom-work-item-types-on-team-services\/","title":{"rendered":"Custom work item types on Team Services"},"content":{"rendered":"

NOTE 9\/13<\/strong>: The custom work item type feature should now be rolled out to all accounts. If you are not seeing it, please reach out to me directly<\/a>.\u00a0<\/span><\/p>\n

NOTE 9\/12<\/strong>: As evidenced by the comments, this feature is still rolling out across Team Services so not all accounts will see the custom work item type feature just yet. I apologize for the delay and will update this blog post when the deployment is finalized. ETA: early this week.<\/p>\n

\"custom<\/a><\/p>\n

With the latest deployment to VSTS, you can now create your own custom work item types (WITs) and place them on the backlog and board level of your choice. Read on for a walk through of the process.<\/p>\n

Create a custom work item type<\/h2>\n

If you do not already have one, you\u2019ll need to create an inherited process<\/a> and migrate your projects to use it. Once you have an inherited process, you\u2019ll notice a new button above the work item types list:<\/p>\n

\"custom<\/a><\/p>\n

Click the New work item type button to\u00a0bring up the dialog. Here, you need to provide a name and, optionally, a description and color for your custom WIT. Currently, you can’t\u00a0rename a WIT, but \u00a0you can update the description and color\u00a0at a later time.<\/p>\n

\"custom<\/a><\/p>\n

\"custom<\/a><\/p>\n

Once you’ve created your WIT, you\u2019ll land on the layout page where you can customize your form layout and add new fields. Your WIT will have default states that you can also modify. Note: the existing limitations for states in the completed category still exist. See this topic\u00a0to\u00a0learn more:\u00a0https:\/\/www.visualstudio.com\/en-us\/docs\/work\/process\/customize-process<\/a><\/p>\n

Add a custom work item type to a backlog and board level<\/h2>\n

Each work item type now has a new \u201cBacklogs\u201d tab that allows the process admin to choose where their custom WITs appear in the Agile experiences. You can’t change the inherited (system) WITs backlog level.<\/p>\n

\"custom<\/a><\/p>\n

Choosing a new backlog level will give you details on the changes that will be made:<\/p>\n

\"custom<\/a><\/p>\n

Commit your change by clicking the \u201cSave\u201d button. Your custom WIT will then begin appearing on the selected backlog and board. You may have to refresh your web browser to see the changes.<\/p>\n

\"custom<\/a><\/p>\n

\"custom<\/a><\/p>\n

Destroy a custom work item type<\/h2>\n

From the overview page of a custom WIT, you can destroy the WIT. Destroying a WIT will permanently delete all work items of that type as well as all references to the WIT. It also frees up the WIT name for reuse.<\/p>\n

\"custom<\/a><\/p>\n

Closing<\/h2>\n

In the next few weeks, we will be adding the ability to disable any WIT. Disabling a WIT will prevent new work items of that type from being created while still preserving existing work items on your backlog, board and queries. It will provide a way to get rid of unwanted inherited WITs and deprecate WITs.<\/p>\n

Please comment or email<\/a> with any feedback or questions.<\/p>\n

Derrick Fu<\/p>\n","protected":false},"excerpt":{"rendered":"

NOTE 9\/13: The custom work item type feature should now be rolled out to all accounts. If you are not seeing it, please reach out to me directly.\u00a0 NOTE 9\/12: As evidenced by the comments, this feature is still rolling out across Team Services so not all accounts will see the custom work item type […]<\/p>\n","protected":false},"author":206,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[227,1],"tags":[],"class_list":["post-20935","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile","category-devops"],"acf":[],"blog_post_summary":"

NOTE 9\/13: The custom work item type feature should now be rolled out to all accounts. If you are not seeing it, please reach out to me directly.\u00a0 NOTE 9\/12: As evidenced by the comments, this feature is still rolling out across Team Services so not all accounts will see the custom work item type […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/20935","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/206"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=20935"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/20935\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=20935"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=20935"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=20935"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}