Work item tracking
Work item tracking resources
Get, create, and update bugs, tasks, and other work items for your team. Queries allow you to use the full power of the work item query language to search for and filter work items. You can use the work item query language to get to each work item that satisfies the query. Work items retain a full history, and you can get each full revision of the work item, or just the updates that were made in each revision. Work items can also be tagged.
Get work items using a query
- Look up the query that you want to use.
- Get the results for that query.
- Get each of the work items by ID.
Update WorkItems in batch
Use Batch WorkItem Update apis to update your workitems in batch.
Update a work item's fields
Link two work items
Create two work items and link them
Attach a file to a work item
- Get the ID of the work item that you want to update.
- Upload the attachment to the attachment store.
- Add the attachment to the work item.
Create a work item
Create a work item. Make sure you provide at least a title. Some types of work items will require values for other fields.
Get a work item's full history
- Get the ID of the work item.
- Get a list of updates made to a work item.
- Get the whole work item as it appeared in any revision.
Delete a work item
Get the fields used in a team project
- Get the types of work items used in a team project.
- Get each work item type to see the fields that it uses. (Skip past the xmlform to fieldinstances.)
Get categories of work items
Use categories of work items to get the types of work items used in a team project for different functions. For example, to see the work items that appear on the backlog, get the requirements category.
Get areas and iterations
Get the area hierarchy or iteration hierarchy for your team project.
Get types of work item relations
Get the available types of work item links that are available in your project collection.
Work item metadata resources
Work items are governed by metadata. Some of the metadata is scoped to a specific team project, and other metadata is scoped to a project collection (like your Azure DevOps Services account's default collection).
Your team project has a set of work item types. Each work item type may belong to a category such as "requirement" or "bug" to define its role in the project. Classification nodes define the set of values that can be used in the area and iteration fields for the work items in the team project.