Re: How to achieve access control through issue dependencies?

> 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. 

You should look into the trunk code.
Permissions based on AttributeGroups has been added.
As long as you don't need read-only access on those restricted
parameters then this should solve what you need.


> 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

I do not think this was ever implemented.

~mck

-- 
To mess up a Linux box, you need to work at it; to mess up your Windows
box, you just need to work on it. 
| semb.wever.org | sesat.no | sesam.no |

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkjt1ysACgkQkdPrePiuutPpJgCeKDMVeKTq6Qw5zOTAxtaJEWNc
m00AoMVpJTbslxd8+dyMZmuuA6mzj6ec
=EJau
-----END PGP SIGNATURE-----