VSTS中关联新父项时，子工作项能否继承父项迭代路径？

Great question! Let’s break this down clearly for VSTS (now commonly called Azure DevOps Server/Cloud) since this is a super common scenario when setting up epic/feature/story hierarchies:

1. Can work items inherit their parent's iteration path? #

By default, VSTS does not automatically inherit the parent's iteration path for child work items. But this is absolutely configurable with work item rules to enforce this behavior.

Here's how you'd set it up:

• Go to your project's process customization settings (either via the Azure DevOps portal or the Process Editor tool)
• For each child work item type you want this for (like Stories under Features), edit the work item type definition
• Add a "Copy value from parent" rule targeting the Iteration Path field. This will ensure any new child items linked to a parent take on that parent's iteration path.

2. Will child items auto-inherit the iteration path when linking to a new parent? #

Again, out of the box, no—changing or adding a new parent link won't automatically update the child's iteration path. But you can extend the rule setup to cover this scenario too:

• When creating the rule, set the trigger to "When a parent link is added or changed"
• Configure the rule to overwrite the child's Iteration Path with the new parent's path whenever this trigger fires.

A few quick notes to keep in mind: #

• These rules are per work item type, so you'll need to set them up for each type in your hierarchy (e.g., Stories, Features) if you want inheritance at every level.
• Existing work items won't get retroactively updated by the rule unless you trigger it (like editing and saving the item, or using a bulk edit operation to reapply parent links).
• You can use the same approach for Area Path inheritance if that's something your team needs.

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