"include sub-areas" 的 Azure DevOps 影响
Azure DevOps Implications of "include sub-areas"
我在 Azure DevOps 中使用 Area Path 进行分类，而不是分成不同的团队。所以我看不到默认待办列表下的所有工作项。我进入“设置”并选择“包括子区域”，然后收到以下警告：
Are you sure you want to include sub-areas?
You have selected the root area path as your team's work area. This
causes two things to happen:
All work items that appear on any team backlog will also appear on
your team's backlog.
All work items under this area path will be updated, which might
impact the performance of your server until the changes are complete.
Are you sure you want to do this? If not, choose Cancel, and the
change will not be made.
#1 是我想要的，但是#2 的含义是什么？工作项更新了什么？分配给用户是否会收到有关更改的电子邮件？
对于#2。这些项目将再次被堆叠以定义选择中所有工作项目的积压订单。我见过有数百万个工作项的实例，在这种情况下，重新计算积压优先级字段并映射到您团队的自定义面板列可能需要一段时间。
此字段不包含在标准电子邮件通知中。
我在 Azure DevOps 中使用 Area Path 进行分类，而不是分成不同的团队。所以我看不到默认待办列表下的所有工作项。我进入“设置”并选择“包括子区域”，然后收到以下警告：
Are you sure you want to include sub-areas?
You have selected the root area path as your team's work area. This causes two things to happen:
All work items that appear on any team backlog will also appear on your team's backlog.
All work items under this area path will be updated, which might impact the performance of your server until the changes are complete. Are you sure you want to do this? If not, choose Cancel, and the change will not be made.
#1 是我想要的，但是#2 的含义是什么？工作项更新了什么？分配给用户是否会收到有关更改的电子邮件？
对于#2。这些项目将再次被堆叠以定义选择中所有工作项目的积压订单。我见过有数百万个工作项的实例，在这种情况下，重新计算积压优先级字段并映射到您团队的自定义面板列可能需要一段时间。
此字段不包含在标准电子邮件通知中。