Skip to content

Latest commit

 

History

History
113 lines (86 loc) · 6.62 KB

add-links-to-work-items.md

File metadata and controls

113 lines (86 loc) · 6.62 KB
title titleSuffix description ms.subservice toc ms.custom ms.author author ms.topic monikerRange ms.date
Link work items to other objects
Azure DevOps
Learn how to link work items to internal Azure DevOps builds, commits, pull requests, and more, and external objects in Git and Team Foundation Version Control repositories.
azure-devops-notifications
show
contperf-fy21q2, cross-project, engagement-fy23
chcomley
chcomley
how-to
<= azure-devops
09/29/2021

Link work items to other objects

[!INCLUDE version-lt-eq-azure-devops]

When you link work items to other objects, you maintain an audit trail of related work for your team. All users can add work item links to the following internal (Azure DevOps) and external (Git) objects.

::: moniker range=">= azure-devops-2020"

Link work items to pull requests

Link your work items to pull request commits, comments, description, and so on.

  1. Enter # to trigger the #ID work item picker in your pull request. You see a list of 50 work items that you've recently modified or are assigned to you.

    :::image type="content" source="media/link-pr-to-work-item.png" alt-text="Screenshot of work item list produced when entering # in PR description.":::

  2. Enter up to five keywords that match the work item type, ID, or title to narrow the list of suggested work items.

    :::image type="content" source="media/keyword-pr-link.png" alt-text="Screenshot of entering keyword after # and resulting work item in search":::

::: moniker range=">= azure-devops-2020"

Set work item state in pull request

[!INCLUDE temp]

Azure DevOps considers the following criteria (in this order) when it attempts to set the state of #mentioned work items:

  1. State
  2. State Category
  3. Keyword

Criteria logic for work item state

The following table describes the criteria logic for work item state.

Criteria Action
If the value matches a state, Then set it to that state.
Else If the value matches a state category, Then set the work item to first state in that category. See the following note.
Else If the value matches a keyword, Then set the work item to matching keyword state. See the following section.
Else Ignore it and do nothing.

Criteria logic for work item keyword

The following table describes keyword logic, which helps with intent matching. For example, you might enter “Resolves”, but you really meant “Resolved”.

Keyword Action
Proposed, Proposes, Propose Set to the first state in the Proposed category.
InProgress Set to the first state in the In Progress category.
Completed, Completes, Complete Set to the first state in the Completed category.
Resolved, Resolves, Resolve Set to the first state in the Resolved category.
Fixes, Fixed, Fix Close work item. Except Bug, which gets set to Resolved.

Note

We don't support category matching on projects using a Hosted XML process. Category matching is only available for projects using an inherited process.

::: moniker-end

[!INCLUDE temp] For more information, see Link work items to user stories, issues, bugs, and other work items

[!INCLUDE temp]

Note

You can't create a work item query to list linked objects. Work item queries only return work items that are linked to other work items. However, you can create a query that lists work items that contain external links. For more information, see Query by link or attachment count.

Related articles