It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×1,207
×239
×12

question asked: Jan 15 '18, 3:27 p.m.
question was seen: 2,596 times
last updated: Jan 16 '18, 3:05 p.m.

Related questions

FAQ - How this Forum works

Why should I use link type "Tracks/Contributes To" instead of "Parent/Child" for Cross Project Plans?

0
1
Andre Gusmao (80●25●40) | asked Jan 15 '18, 3:27 p.m.

This is a well known scenario: Project Area A has the plan Items (Backlog Items), which are linked to execution items (Tasks and Defects) in Project Area B. Project Area A is owned by the Business, who will create and track backlog items. Project Area B is owned by Development, who will break down the backlog items into tasks and defects as needed.

My question is: why should I use the "Tracks/Contributes To" relationship between plan items and execution items instead of the "Parent/Child" relationship?

I know that both relationship types can be used across different project areas. I also know that the "Parent/Child" relationship does not require the project areas to be associated, plus the plan item is shown in the plan.

Are there any other reasons why I should use "Tracks/Contributes To"?

Thanks!!

Accepted answer

1
permanent link
Ralph Schoon (63.1k●3●36●46) | answered Jan 16 '18, 12:32 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 Basically parent/child relationships have a dedicated functionality e.g. roll up in plans ONLY WITHIN ONE PROJECT AREA. Parent child can be created across project areas, but the built in capabilities don’t work.


Parent child is also only 1:N.

Tracks/ contributes to 
  1. Works across project areas
  2. Work across multiple ccm repositories
  3. Is the link type that is supported in cross project plans
  4. Is M:N

Andre Gusmao selected this answer as the correct answer
Comments
2
Guido Schneider commented Jan 16 '18, 3:05 p.m.

We are using Parent/Child cross PA a lot. It's working fine within one CCM instance.

Specially in a environment, where you do e.g. a Feature/Story breakdown and move the Story into another team in another PA, for implementation.

But do not expect, plans with working progress bars etc. over PA boarders.

Within Report Builder you can use such parent/child links cross PA also for progress reporting, by selecting both PA.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.