Work Item relation semantics
One answer
torbitz wrote:
I believe that most of the relationship types have no special semantics
for RTC. They exist primarily so you can document work item
relationships in a way that other people can see. RTC usually doesn't
behave differently based on whether a particular relationship exists or not.
I can think of two case where relationships do affect behavior, though
there may very well be others that I don't know about.
1. Parent/child relationships affect how work items are presented in
iteration plans and in certain reports. (I don't know the details,
since our team doesn't make much use of iteration plans.)
2. A work item can't be resolved as a duplicate unless a "Duplicate of"
relationship exists.
I have a questions regarding relations between Work Items in RTC.
What is the semantics behind these relations?
I believe that most of the relationship types have no special semantics
for RTC. They exist primarily so you can document work item
relationships in a way that other people can see. RTC usually doesn't
behave differently based on whether a particular relationship exists or not.
I can think of two case where relationships do affect behavior, though
there may very well be others that I don't know about.
1. Parent/child relationships affect how work items are presented in
iteration plans and in certain reports. (I don't know the details,
since our team doesn't make much use of iteration plans.)
2. A work item can't be resolved as a duplicate unless a "Duplicate of"
relationship exists.