No, I think that will need two separate actions. No single client knows about the action results of another, so even if you changed the source Fixlets to only be relevant on one computer or the other, the computer writing the ticket would not know the success of the computer running the task (and in fact the ticketing action could execute before the task action).
I think you need to rearchitect the workflow so an API from the server is dealing with your ticketing, rather than having individual clients do that part