I've been playing around with this as well. Any chance to get an idea of a workflow to be build with this? One way I could imagine doing is by trying to build our workflow into ITSM 2.0. That would then probably translate to:
- Create change - Add WO: build the change - Add WO for approval: one WO for each CAB member that needs to approve - Add rest of the WO's describing the work to be done - Add PIR WO - Add condition: if WO status of the build change WO is closed, set Change state to Pending Approval, and set WO state of approval WOs to ready (?) - Add condition: if Change state of all WO's for approval are set to accepted, Change state should be set to approved. - Add condition: as soon as one of the other WO's changes state to "in progress" set the change to "in progress". - Add condition: as soon as all WO's change to "closed", set Change state to Pending PIR - Add condition: as soon as Pending PIR WO has been closed, the Change can be closed too. However, there are some issues here: - I hope the complete logic can be saved in templates as well :-) - The approval WO's are a bit... uneasy. When I can already set the CAB, it would be cool if there was some mechanism to automagically request approval from each CAB member. - Use Ready or Accepted for the WOs? - Not sure how I can do a successful close/failed/... depending on the PIR. BUT, then again, maybe I've totally overseen something here. I'd really be happy if somebody could give an example of such a workflow. And I guess, I'm not the only one :-) Thanks, Arthur
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/
