What is the difference between "resolves/resolved by" and "tracks/contributes to" link type in RTC 4.0?
In RTC 4.0 there was an new link type introduced to support crossproject reports. This link type is called "tracks/contributes to".
In RTC 3.0.1 there was already a link type (and is still available in RTC4.0) calles "resolves/resolved by".
This two linktypes are similar in meaning. Both are RTC internaly linking work items together.
What are the technical and detailed differences between this two linktypes? What is not possible with which type but with the other.
Is there a possibility to migrate from "resolves/resolved by" to "tracks/contributes to" if this new link type provides more functionality? Today we are using the "resolves/resolved by" for highlevel planitem (e.g. themes) linked to epics/stories to be able to track the implementation of this themes (synonym for requirements/features).
In RTC 3.0.1 there was already a link type (and is still available in RTC4.0) calles "resolves/resolved by".
This two linktypes are similar in meaning. Both are RTC internaly linking work items together.
What are the technical and detailed differences between this two linktypes? What is not possible with which type but with the other.
Is there a possibility to migrate from "resolves/resolved by" to "tracks/contributes to" if this new link type provides more functionality? Today we are using the "resolves/resolved by" for highlevel planitem (e.g. themes) linked to epics/stories to be able to track the implementation of this themes (synonym for requirements/features).
2 answers
The contributes-to link type has planning semantics. In particular, in a Project Schedule plan, the estimated cost/time of a work item is added to the accumulated time of the work item that it contributes to. The "resolves" link type does not have this semantics.