User Reference CCK

This is the intended behaviour. The logic is to give to the workflow admin the ability to treat the user reference field as a role because in many practical situations this is needed. The single member of that virtual role is the user referred to by that field in a specific instance of the node.

For example, a Job Candidate content type would have a user reference field called Interviewer, referring to the employee who conducted the interview. Workflow Fields gives the ability to choose Interviewer as the only role that can edit the Job Candidate other fields such as hiring recommendation.

Automatically closed -- issue fixed for two weeks with no activity.