Building dependancies between Work Item Instances
Hi,
We want to build a strict sequence of work items:
Task c, cannot be started before task b,( and task b cannot be started before a, and so on).
How can we define , prepare such a behaviour at the process template level (or in ProjectArea)?
At the moment (in the Process Template) at Project Area Initialization Setup Project Server Follow/On actions, we have defined 7 Work Item Template. We would like to be able to set up some kind of 'dependancies|blocking' mechanism between these Work Items. (once again, the goal is that a task cannot be started before the previous is finished)
Any ideas? (we don't mind if the solution is very complicated or elaborate...)
We want to build a strict sequence of work items:
Task c, cannot be started before task b,( and task b cannot be started before a, and so on).
How can we define , prepare such a behaviour at the process template level (or in ProjectArea)?
At the moment (in the Process Template) at Project Area Initialization Setup Project Server Follow/On actions, we have defined 7 Work Item Template. We would like to be able to set up some kind of 'dependancies|blocking' mechanism between these Work Items. (once again, the goal is that a task cannot be started before the previous is finished)
Any ideas? (we don't mind if the solution is very complicated or elaborate...)
2 answers
Hi,
what we have are the blocks/depends links between work items, but these are not enforced in any way and the Setup follow-up action cannot be configured to create links between the work items.
If you wanted you could write your own setup follow-up action that supports links between work items and an operation participant for the 'save work item' operation that checks that all dependencies are resolved before a work item can be set 'in progress' or be resolved.
I've opened enhancements 59096 and 59097 to capture your requests.
Regards,
Christof
Jazz Work Item team
jessekiki wrote:
what we have are the blocks/depends links between work items, but these are not enforced in any way and the Setup follow-up action cannot be configured to create links between the work items.
If you wanted you could write your own setup follow-up action that supports links between work items and an operation participant for the 'save work item' operation that checks that all dependencies are resolved before a work item can be set 'in progress' or be resolved.
I've opened enhancements 59096 and 59097 to capture your requests.
Regards,
Christof
Jazz Work Item team
jessekiki wrote:
Hi,
We want to build a strict sequence of work items:
Task c, cannot be started before task b,( and task b cannot be started
before a, and so on).
How can we define , prepare such a behaviour at the process template
level (or in ProjectArea)?
At the moment (in the Process Template) at Project Area Initialization
Setup Project Server Follow/On actions, we have defined 7 Work Item
Template. We would like to be able to set up some kind of
'dependancies|blocking' mechanism between these Work Items. (once
again, the goal is that a task cannot be started before the previous
is finished)
Any ideas? (we don't mind if the solution is very complicated or
elaborate...)
Hi,
what we have are the blocks/depends links between work items, but these are not enforced in any way and the Setup follow-up action cannot be configured to create links between the work items.
If you wanted you could write your own setup follow-up action that supports links between work items and an operation participant for the 'save work item' operation that checks that all dependencies are resolved before a work item can be set 'in progress' or be resolved.
I've opened enhancements 59096 and 59097 to capture your requests.
Regards,
Christof
Jazz Work Item team
Thx, Christof!
I had found depends/blocks and tried it as well(missing enforement:( ). Anyway, I'm looking forward to the enhancement. :D