CODEWITHSUNDEEP
rally
Tore
Tore

Reputation: 1264

Confusion about HierarchicalRequirement fields

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:

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:

  1. Did I define the three fields and their uses correctly? If so,
  2. Why are there 3 when 2 (Parent and Feature) would suffice?
  3. Are there other cases I am not considering?

Thanks

Upvotes: 1

Views: 469

Answers (1)

Charles Ferentchak
Charles Ferentchak

Reputation: 1237

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.

Upvotes: 1

Related Questions