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.
When you create a pull request, you can set the state value of the linked work items in the description. Follow the syntax: state value: #ID.When you merge the pull request, the system reads the description and updates the work item state. In the following example, we set work items #300 and #301 to Resolved, and #323 and #324 to Closed.
Linked objects are grouped under their link type, with a count within each group. You can expand or collapse each group, and sort within each group by State, Latest Update, or Comment by choosing the corresponding column title.
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.
One of the main ways Azure DevOps supports traceability is by linking objects. Work items link to Git branches, commits, pull requests, builds, and more. Work item forms provide two controls to show and quickly navigate to development objects. The Deployment control is described in this article, and the Development control is described in Drive Git development from a work item.
As shown in the following image, the Deployment control shows release information for two release stages those work items that have been linked to a Git commit or pull request for a release pipeline configured to integrate with Azure Boards.
Work items linked to a Git repository branch, commit, or pull request participate in populating the Deployment control.You can view all links through the work item form Links tab.
To learn how to associate work items to commits, see Drive Git development from a work item or Link to work items from other objects. To view objects linked to a work item, see View list of links for a work item.
To view and navigate to the builds and releases linked to a work item, choose the Links tab. Links are grouped under their link type and listed in the order they were created. Choose the State or Latest Update column headings to sort by the column. Links prefaced with the red exclamation mark indicate that the build, release, or other object has been deleted. This indicator occurs because of retention policies, which automatically delete these objects after a certain time period has passed.
Once a work item is linked to a commit or pull request, it will continue to show up as part of the release stages. For example, if you have a work item that didn't pass testing criteria, you may want to remove it from the builds and releases.
To remove the work item from participating in future builds and releases, delete the link to the most recent commit and pull request. You can do that by opening the Links tab for the work item as shown in the previous section.
Hi am new to Azure devops and try to understand Repos and Boards. Is there a way to link both (i.e Azure Repos and Azure Boards)Any pointers would be useful. Basically, I want to understand whether code commits can be connected to link Boards tasks or User story.Thanks.
Link types you use to link work items are subject to certain restrictions based on their topology. Use the guidance provided in the following tables to choose which link type to use based on the types of queries and reports you'll want to create. To learn more about the different topologies, see Link type topologies and restrictions.
Each work link type defines the link labels, topology type, and restrictions that are used when links between work items are constructed. For example, the parent-child link type defines two labels: Parent and Child. The link type also supports a hierarchical or tree topology, and prevents circular references from being created between work items.
Use this directional link to create one-to-many relationships between a single parent to one or more child items. Use to organize work item within a hierarchy. You can quickly create this hierarchy among backlog items using the mapping function or among backlog items and tasks using the sprint backlog or Taskboard.
Use to link test cases to shared parameters. Use to link Test Cases to Shared Parameters to support the ability to repeat a test with different data. In general, you wouldn't add this link type to a scoped links control. To learn more, see Repeat a test with different data.
Use this non-directional link to create links between any set of work items. Use to link work items that are at the same level, such as two user stories that define features that overlap one another. The Related link type creates simple relationships with few restrictions.
Topology type: DependencyLink category: System-definedChoose Predecessor link type when linking to a work item that should be completed before the work item you're linking from. Choose Successor link type when linking to a work item that should be completed after to the work item you're linking from.
Use this directional link to create links between any set of work items, but not ones that would create closed loops. Use to track tasks that must be completed before others can be started. When you plan work using Microsoft Project, linked tasks are represented as predecessor-successor links in Azure Boards. Typically used to track work that must be completed before beginning work on predecessor items.
Link test cases to work items, such as bugs, user stories, requirements, and product backlog items. Use to track test cases that test user stories (Agile), product backlog items (Scrum), or requirements (CMMI). Can also link to other work item types such as bugs, issues, or tasks. For on-premises Azure DevOps, there are several SQL reports that depend on these links. See Review team activities to support useful reports.
Use to link test cases with shared steps. You share steps between test cases to avoid having to create multiple entries of the same sequence of steps. To learn more, see Share steps between test cases.
External link types are system-defined link types that support linking work items to other objects stored within Azure DevOps as shown in the following image. A work item's External Link Count corresponds to the sum of all links defined with an external link type.
The following table describes the external link types you can choose when adding a link type from a work item or test case. Also, you can use specify one of these link types to scope a links control using the ExternalLinksFilter XML element.
Used to link a release to a work item. The system creates a link of this type when a user enables the Report deployment status to Work option for a release definition. To learn how to set this option, see Release pipelines, How do I integrate and report release status?
You can only link to GitHub artifacts whose repositories you have connected to Azure Boards. To create that connection, see Connect Azure Boards to GitHub. To learn more about linking to GitHub artifacts, see Link GitHub commits, pull requests, and issues to work items.
Remote work link types are system-defined link types that support linking work items defined in different organizations. Organizations must be managed by the same Azure Active Directory as described in Connect your organization to Azure Active Directory.
Use this directional link to create links between work items that have dependencies and are defined in different organizations. Organizations must be managed by the same Azure Active Directory. Typically used to track change requests made to requirements.
You can list link types supported by your organization with the az boards work-item relation list-type command or the Work Item Relation Types - List REST API command. To get started, see Get started with Azure DevOps CLI.
The default json format provides additional information about the attributes defined for the link types. For example, the information for the link types Produces For and Consumes From are listed as follows.
Indicates whether the link type allows or (true) or restricts (false) circular relationships. For example, tree type links restrict circular relationships. For more information, see LinkTypes elements reference.
Indicates whether the link type is directional (true) or not (false). Directional link types are defined in pairs with a forward and reverse component. For more information, see LinkTypes elements reference.
Indicates whether the link type is editable (true) or not (false). You can only add and edit custom link types for on-premises deployments using witadmin Manage link type command-line tool. System link types always have editable=false.
Indicates whether the link type supports linking to a remore work item (true) or not (False). Link types with remote=false require that the target work item resides in the same organization or collection as the origin work item.
Link work items to other work items to manage dependencies and see relationships within work. You can link work items within your project or to work items within another project in your organization. Use different link types to support different business goals. You can also link work items to other objects such as builds, commits, versioned items, or network resources.
Link work items to other work items to manage dependencies and see relationships within work. You can link work items within your project or to work items within another project in your collection. Use different link types to support different business goals. You can also link work items to other objects such as builds, commits, versioned items, or network resources.