Update: Monday, May 8th 2017 17:02 UTC

This issue impacts users trying to do administrative updates to their work item templates. Updates that try to add an existing field to a “custom work item type” will encounter an error during customization attempt. Users doing normal interactions with work-items (read, create, updates, search) are not impacted.

We’ve isolated the source of this issue to a bug and have developed a hotfix that will resolve the problem. The hotfix is being deployed and we estimate it will take ~6-8 hours to fully deploy globally.

• Work Around: None available.
• Next Update: Before Monday, May 8th 2017 23:15 UTC

Sincerely,
Tom

Update: Monday, May 8th 2017 15:35 UTC

Our DevOps team continues to investigate issues with Work Item Tracking Feature of TFS. Root cause is not fully understood at this time, though it is suspected to be bug in our code. We currently have no estimated time for resolution.

• Next Update: Before Monday, May 8th 2017 18:45 UTC

Sincerely,
Shubhra

Initial Update: Monday, May 8th 2017 13:41 UTC

We are investigating Performance Issues with Work Item Tracking feature of TFS. Some subset of users from South Central US, North Central US, Central US, Australia and West Europe regions may experience following error while working with customized Work Items.

VS402805: Work Item type with reference name ‘System.WorkItemType’ could not be found in process ‘6b724908-ef14-45cf-84f8-768b5384da45’

• Next Update: Before Monday, May 8th 2017 14:45 UTC

Sincerely,
Mahesh