Why should I use link type "Tracks/Contributes To" instead of "Parent/Child" for Cross Project Plans?
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.
|
Accepted answer
Ralph Schoon (63.3k●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
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.
|
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.