> Yes, that's the straightforward reasoning. Just notice that workflow > actions not necessarily have to modify ticket status. The most common > example is leave action. I mean: deleting or adding relation does not change ticket at all, IOW this is not supposed to be ticket.save_changes action. Currently, user is required to have *_CHANGE permission on resource (e.g.) to change its relation but this can be easily changed in future. I can imagine the business requirement that user can make relation between tickets that he/she doesn't have change permission.
Cheers, Andrej
