Charlie

The UI for creating a trigger allows me to set a user field change as a trigger, and then a ticket field as the action, so it implies this is possible (see screenshot). But it doesn't do anything when I actually change the user field, so I'm confused.

I've tried both the trigger approach and simply having both fields and values exist on both the user and the ticket, but I can't get the ticket field values to update after the ticket has been raised. The ticket value is set correctly at the point of creation, based on the user field value, but if I subsequently change the user field again, the ticket field does not update, even if I have manual triggers set up to do this. Should this work?