As far as I can tell, when the actual SQL select statement is constructed (starting on line 337 of moodle/user/index.php), the WHERE condition is somehow not excluding the "doanything" users found earlier. (line 346)
For my own temporary purposes, I modified the WHERE condition to exclude my admin user using a hardcoded username, but this is hardly a real solution for all.
Is this a known bug, or is there something I am missing here?
I too have noticed this.
My problem extends to the fact that I am the site admin and also a teacher of courses. All my courses now list me as "administrator" when in pervious moodle versiosn I was listed as a teacher.
I realize I could create another role for me as teacher, but don't really want to manage 2 user accounts.
I created a new role called "sixth form students" basically intented to be the same as a normal student with a few extra features..
at our school Standard students are not allowed to use chat, sixth formers can...
however, whilst i seem to have cloned the student and made the modifications, the new Sixthformers, now appear in all participant lists for all courses...
I assigned the sixthformer role at site level.
have i done something wrong?
I too found this, but also found that even "students" assigned at the site level become members of all courses.
It will take time figuring out roles.