on the bootcamp training, i once asked about this (version 7.1.4), and the instructor said that we can somehow using a windowsless action to perform assignment using Incident From instead and manipulate the suggesteg group and the analyst and then pass them to automatic assignment.
Thanks Olive - Well that sounds interesting and talking out loud I can see a way of storing the current group/user on the incident. Then a windowless action could display this, allow someone to change the values and then have anther action after that to do the assignment. I've used your idea before to allow people to change impact/urgency from an action rather than just changing them. It works until you have two people do the same thing at the same time as you are using the same attribute on the incident in this way. But the window of opportunity for this to happen is very small.
So food for thought and I shall report back
All the best
Can you use a Value Type prepopulation from Incident.Currnet Assignment.Group?
Admittedly when I look at a normal action, I don't get an Action Value option which I do get in an auto action..... Was that different in 7.1?
Well it turns out that on a custom action you cannot use filters that refer to relationships like incident/current assignment until the action has actually been saved. So the trick (from Stu) is to use an attribute on the incident to store your 'user assignment' and create a windowless action off incident with a window (yes - I know!). This action is launched from the incident, so it does have access to current assignment. You can thus create a filter on this 'user assignment' attribute in incident which refers to the run-time value current assignment.group which is all you need.
The upshot is that although you cannot display current group, you can offer a drop down which just lists the analysts in the current group the incidents is assigned to.