关于 HierarchicalRequirement 字段的混淆 [英] Confusion about HierarchicalRequirement fields

问题描述

相关父级的用户故事有 3 个不同的字段，我们对此有些困惑.

There are 3 different fields for User Stories for a related parent, and we have run into some confusion about them.

据我所知:

• Parent 字段用于作为另一个用户故事的直接父级
• PortfolioItem 字段用于 直接 父级，即 Feature
• Feature 字段用于父母(直接或通过一个或多个美国父母)是功能

• The Parent field is for a direct parent that is another User Story
• The PortfolioItem field is for a direct parent that is Feature
• The Feature field is for a parent (direct or via one or more US parents) that is a Feature

如果您有 Parent 和 Feature 字段，难道您不能比较这两个字段以查看直接父项是美国还是 PI(因此不需要 PortfolioItem 字段)?在我看来，对此的一种解释是，最初只有 2 个字段，Parent"和PortfolioItem"，但这限制了查看相关功能的能力，除非您遍历用户故事的层次结构，直到一个具有功能的设置为父级.

If you have the Parent and Feature fields, couldn't you compare the two of them to see if the direct parent is a US or a PI (thus rendering the PortfolioItem field unnecessary)? It seems to me the one explanation for this is that originally there were only 2 fields, "Parent" and "PortfolioItem", but that restricted the ability to see an associated feature unless you traversed the hierarchy of User Stories up to one with a Feature set as the parent.

所以，我的问题是:

1. 我是否正确定义了三个字段及其用途?如果是这样，
2. 为什么有 3 个，而 2 个(父级和特征)就足够了?
3. 还有其他我没有考虑的情况吗?

谢谢

推荐答案

投资组合项字段早于特征字段.当我们将它添加到 API 时，我们还没有创建在我们的层次结构中滚动"信息的技术.案例一和案例二主要用于显示网格和板中显示的直接父级(如果有).

The portfolio item field predate the feature field. When we added it to the API we had not yet created the technology to "Roll down" information in our hierarchy. Cases one and two are mainly used to show the direct parent (if any) that is shown in grids and boards.

为了向后兼容，我们可能会保留组合项字段.

We will probably keep the portfolioitem field around for backwards compatibility.

这篇关于关于 HierarchicalRequirement 字段的混淆的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！