Has anyone ever daisy chained Service Desk tickets
The scenario I have is that we run a change process where the user logs a change request for pre-install work. Once approved this spawns a child ticket for that work. I was wondering if there was a way to trigger a second change to do the implementation work once the status of the first change is complete.
Yes, Processes can do this.
If a stage has been finished, the next stage with its child tickets is fired off etc.