问题
There are 3 different fields for User Stories for a related parent, and we have run into some confusion about them.
As I understand it:
- 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
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.
So, my questions are:
- Did I define the three fields and their uses correctly? If so,
- Why are there 3 when 2 (Parent and Feature) would suffice?
- Are there other cases I am not considering?
Thanks
回答1:
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.
来源：https://stackoverflow.com/questions/18364905/confusion-about-hierarchicalrequirement-fields