Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.

Automating State Transitions

Customers and partners may want to automatically transition work items from state to state based on events that occur elsewhere in Team System or on events that occur outside Team System, for example, from a call tracking tool. The work item type model and the Work Item Tracking API are extended to support automatic transitioning of work items by other systems.

NoteNote

The Work Item Tracking API is part of the Microsoft Visual Studio 2005 Team System SDK that you can obtain from the Microsoft Visual Studio Developer Center.

For example, a tool is preset to automatically transition a work item to "Resolved" after the user checks in a change. However, as an integration provider, you do not know what state the work item type author has declared as "Resolved.” The author may mean Resolved, Closed, Completed, Ready For Test, Include In Build, and so on. One option would be to require all work item type authors to include a state explicitly named "Resolved.”

That solution too restrictive and is also poor from an international perspective because it does not enable localization of states. Instead, system integrators can declare an action such as "Check-in" or "Complete" that induces an automatic transition for work items. The work item type author would then declare this action on the appropriate transition.

In This Section

Related Sections

See Also

Community Additions

ADD
Show:
© 2015 Microsoft