By stodge on

I've been playing with using organic groups to create a basic bug tracker. I like the Project module but one feature I need is control of user access on a per project and per role basis. So I want to give specific users read&write access to project A, some users have read-only access to project A and all other users are blocked completely.

I thought I could use organic groups and specify a project (from the project module) as a group node. Which seems to work fine, though there's a problem with project_issue and the group details block.

I'm also trying to create something using the CCK but that's proving quite difficult as there are so many views and so much logic to implement somehow that it hurts my brain.

So are there any other options apart from the above?

Thanks

⋅ Categories: Drupal 6.x

Comments

nlindley’s picture

nlindley commented

How about using some sort of taxonomy + access control system?

stodge’s picture

stodge commented

Good point - I'll look into that. Thanks

southweb’s picture

southweb commented

I just spent a day crafting a module with a bunch of hooks and overrides to achieve exactly this the hard way. Took me down some interesting avenues though - basically had to create my own view_access plugin and do some stuff with node api. Ended up creating roles that matched project names, and assigning these.

http://www.southweb.co.nz

truyenle’s picture

truyenle commented

Any progress on this Stodge! I am facing the same issue.