Planned Date<\/strong><\/p>\n<\/td>\n Feature<\/strong><\/p>\n<\/td>\n<\/tr>\n Q3 2016<\/p>\n<\/td>\n Q4 2016<\/p>\n<\/td>\n With states and fields available, the next step is allowing users to create their own custom work items.\u00a0 When you create a new work item, it will have the initial set of system fields along with a “new” and “closed” state.\u00a0 Of course, you will have full control of these work item types and can add as many additional fields and states as you want.\u00a0 You’ll also have full control of the layout.\u00a0 Adding custom work item types is great, but what most customers really want to do is add those new work item types to the backlog; adding a custom work item to the backlog will be as simple as checking a checkbox.<\/p>\n Custom identity fields to track ownership, assignment, etc. are another scenario we want to enable. Like with picklists, we want to make this significantly simpler than exists today on TFS. Identity will be another field type available from the add field dialog and it will display with the avatar image, display name and contact card on the work item form.<\/p>\n In TFS, process administrators can use rules on fields to model custom business logic.\u00a0 While this is a powerful customization, maintaining the rules in XML is quite difficult .\u00a0 This is another area we want to significantly simplify through a fit for purpose UI.\u00a0 We are looking at modeling rules through triggers and actions, similar to how service hooks work on the service today.\u00a0 In addition to wrapping this experience with a UI, we’re looking to add new triggers and actions to filter the new picklist and identity fields.<\/p>\n Once we have work item types, all the key process assets will be in place and we can release public REST APIs for customization.\u00a0 Our plan is to provide two sets of APIs: a read only resource that shows the full, composed process as well as a separate set of resources for doing create, update, and delete operations at the inherited process level.\u00a0 Some advanced functionality will exist in the APIs that we don\u2019t have UI for yet.<\/p>\n\n \n \n \n \n
\n \n \n \n
Creation of custom work item types [Shipped 9\/2016]<\/a><\/h3>\n
![\"Adding](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/6\/2019\/05\/Figure1-NewWorkItemType1.png\")
<\/a><\/a>Add Identity fields to existing work item types<\/a><\/h3>\n
<\/a>Define simple business logic and rules<\/h3>\n
REST API support for customization<\/a><\/h3>\n
Improvements to custom states & picklists<\/h3>\n