RTC Links types definition
2 answers
Hi Fabiano,
You can find the resource from a similar discussion https://jazz.net/forum/questions/132522/is-there-any-document-about-definition-of-work-item-link-type
In addition, the following documents may helpful:
https://jazz.net/wiki/bin/view/Main/WorkItemAPIsForOSLCCM20#RTC_Work_Item_Vocabulary
https://jazz.net/wiki/bin/view/Main/CALM2010LinkTypes
You can find the resource from a similar discussion https://jazz.net/forum/questions/132522/is-there-any-document-about-definition-of-work-item-link-type
In addition, the following documents may helpful:
https://jazz.net/wiki/bin/view/Main/WorkItemAPIsForOSLCCM20#RTC_Work_Item_Vocabulary
https://jazz.net/wiki/bin/view/Main/CALM2010LinkTypes
Thank you for your answer. I can not understand especially the rules around link types. What are pre-conditions for use each links. For example : If a work item have a link Parent, I can't add other Parent. I Understand this rule, but in other links cases as Blocker/Depends On , Predecessor/Successor, etc. Exists a documentation about this?
Comments
I couldn't find a document to explain all link type constraint.
For Blocker/Depends On, it seems not have any constraint. Please see enhancement request:
The depends-on/blocks relationship should produce an end/end schedule dependency
For Predecessor/Successor, you can refer to https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.team.apt.doc/topics/c_dependencies.html&scope=null
as you've found there is only one rule.. a child can have only one parent.
beyond that there is no enforcement of the semantics.
predecessor/successor only matter in the formal project template. not agile/scrum
scrum doesn't care about schedule. so depends/blocks cannot have a schedule semantic.
ok, but lacks clear documentation about it.