Azure DevOps：如何在Kanban冲刺任务板显示任务与测试工件的父级关联

Great question! I’ve dealt with this exact scenario in Azure DevOps before—by default, the Kanban board doesn’t surface parent relationships to test artifacts (test cases, suites, plans) the same way it does for requirements and bugs, but we can fix that with a few configuration tweaks. Here’s what you need to do:

1. Add the Parent Field to Kanban Cards #

The simplest fix is to make the parent relationship visible directly on task cards:

• Open your sprint’s Kanban board in Azure DevOps.
• Click the gear icon (Board Settings) in the top-right corner.
• Navigate to the Cards tab.
• In the Card Fields section, click Add field and select the Parent (or Parent Work Item) field from the list.
• Save your changes. Now every task card will display its parent test artifact, just like how bugs show their parent requirements.

2. Verify Parent Work Item Type Permissions #

If you’ve already set up the parent relationship but it’s still not showing up, double-check that your process allows tasks to have test artifacts as parents:

• Go to your project’s Project Settings → Work Items → Process.
• Select the process your project uses (e.g., Agile, Scrum, or a custom inherited process).
• Find the Task work item type, then open its Parent/Child settings.
• Ensure that Test Case, Test Suite, and Test Plan are listed in the Allowed parent work item types section. If not, add them (note: this only works for inherited processes—you can’t modify Microsoft-hosted default processes directly, so you’ll need to create a custom inherited process if you’re using a default one).

3. Group Tasks by Parent Test Artifact #

For even better visibility into test-related task planning, use the board’s grouping feature:

• On the Kanban board, look for the Group by dropdown at the top of the board.
• Select Parent from the options. Your tasks will now be grouped under their parent test artifacts, making it easy to see all tasks tied to a specific test case, suite, or plan at a glance.

One quick note: Azure DevOps prioritizes requirement-bug relationships out of the box, so test artifacts don’t get the same default treatment—but these configurations will bridge that gap and let you manage test-related tasks alongside your other sprint work seamlessly.

内容的提问来源于stack exchange，提问作者Neal