nexedi/slapos.core!417

Virtual Master's manager are responsible to handle the tickets through their worklist.
Not user.

Virtual Master's manager can send email from the Ticket to directly ping a user.

I don't get why there are 2 transitions for now.

Use causality category instead of aggregate, to link the Ticket to the context document (instance, node, ...).
Aggregate must be used to define the item of the movement resource.

Break the parameters and use the context to define the causality value.

limit parameter with count is meaningless, as count return 1 result