How to achieve access control through issue dependencies?

Hi everybody,

 

I'm trying to achieve that one group of scarab users have access (RW) to all parameters of an issue, while another group have access (RW) to only selected parameters.  This is similar to the use case described in User guide <http://www.solitone.org/scarab-trunk-doc/docbook/scarab-user-en.html#N10503> . Proposed solution is to use two modules and to create dependency between issues in these two modules. I have already tried this, but without expected results. I expected that dependency will ensure that change of a parameter in first module will also effect in similar change of the same parameter in second module and vice versa. I tried to set up all types of dependency, however it didn't work. Anyone has a clue what am I doing wrong? Many thanks!

 

Michal