problem with preventing the customer from changing state of the ticket
Dear list, I'm playing with test installation of OTRS. Most things work as advertised, but I have one problem I cannot find a solution to... (I did read TFMs and am fairly sure, that this was not on the list). To the problem: I'd like to stop the customer from changing the ticket state after it was moved to queue to which that customer has read only access (via group access) I've enabled customer groups, the customer is a member of the specified group with ro access, the queue belongs to the specified group. The behaviour is the same in in 2.1.7 and in 2.2 beta (the platform is Debian, both installations from packages, the latter is the experimental package rebuilt for etch). Did anyone encounter such a problem? Best regards Miroslaw Baran
Dear list, I wrote on 6/28/07:
I'd like to stop the customer from changing the ticket state after it was moved to queue to which that customer has read only access (via group access)
I've enabled customer groups, the customer is a member of the specified group with ro access, the queue belongs to the specified group.
Should I assume that this is buggy behaviour and report it as bug or am I overlooking something? Additional info: 1) Both agents and customers are authenticated to AD domain controllers using LDAP backend. 2) I tried also restricting the possibility of changing state using ACL, to no effect. Attached is slightly neutered Kernel/Config.pm file, so that you could see what was changed. As this is the only problem that prevents me from introducing OTRS in our part of the organization, I'd really like to find the culprit... Best regards Miroslaw Baran
participants (1)
-
Mirosław Baran