Work items dependencies
6 answers
Hi Claudia
There are two link types that have additional semantics:
Parent/Children: this is used by Agile Planning, e.g. all Tasks needed to implement a Story are children. The Plan will show children and parents and for the parent will aggregate the values from the children for progress computation.
Duplicates/Duplicate Of: this is used by Work Items when resolving a defect as 'Resolved' 'Duplicate'. When such a link is added the state of the duplicate is changed and when a link is removed, the item is reopened.
For other link types nothing is implemented as special semantic.
Regards
Marcel
Jazz Work Item team
There are two link types that have additional semantics:
Parent/Children: this is used by Agile Planning, e.g. all Tasks needed to implement a Story are children. The Plan will show children and parents and for the parent will aggregate the values from the children for progress computation.
Duplicates/Duplicate Of: this is used by Work Items when resolving a defect as 'Resolved' 'Duplicate'. When such a link is added the state of the duplicate is changed and when a link is removed, the item is reopened.
For other link types nothing is implemented as special semantic.
Regards
Marcel
Jazz Work Item team
Hi Claudia
There are two link types that have additional semantics:
Parent/Children: this is used by Agile Planning, e.g. all Tasks needed to implement a Story are children. The Plan will show children and parents and for the parent will aggregate the values from the children for progress computation.
Duplicates/Duplicate Of: this is used by Work Items when resolving a defect as 'Resolved' 'Duplicate'. When such a link is added the state of the duplicate is changed and when a link is removed, the item is reopened.
For other link types nothing is implemented as special semantic.
Regards
Marcel
Jazz Work Item team
Is there Parent Child state dependency checking? Meaning I cannot close/resolve a Parent unless all the child have been resolved?
With RTC 1.x there was a warning issued if you had inconsistent settings. No error and nothing prevented one from making inconsistent changes. This can be done using a custom condition though - I have seen a prototype.
Ralph
Is there Parent Child state dependency checking? Meaning I cannot close/resolve a Parent unless all the child have been resolved?
Ralph
Hi Claudia
There are two link types that have additional semantics:
Parent/Children: this is used by Agile Planning, e.g. all Tasks needed to implement a Story are children. The Plan will show children and parents and for the parent will aggregate the values from the children for progress computation.
Duplicates/Duplicate Of: this is used by Work Items when resolving a defect as 'Resolved' 'Duplicate'. When such a link is added the state of the duplicate is changed and when a link is removed, the item is reopened.
For other link types nothing is implemented as special semantic.
Regards
Marcel
Jazz Work Item team
Is there Parent Child state dependency checking? Meaning I cannot close/resolve a Parent unless all the child have been resolved?
Did this question ever get answered?
The new and noteworthy for 3.0 Beta 2 has this:
Pre-condition that checks child states
There is a new precondition that enforces that a parent work item can only be resolved if all children are resolved. It also prevents adding children to already resolved parents.
I haven't used 3.0 or investigated the feature myself.