[consulting] Case Tracker 4.7 released

[Khalid B]

My setup is like this:

I have two CCK types, project and task.

Then under admin/settings/og

Have the following selected:

- New groups don't appear in the groups directory. Administrators control
the directory exclusively.
- New groups don't appear in on the registration form. Administrators
control the form exclusively.
- Audience checkboxes (unchecked)
- Audience required (set to required)
- Presentation style : Group by content type
- Group home page node types: group only

This way, the groups are invisible, and people have to be added explicitly
to a group
and hence the other groups are invisible to a given person who has access to
group A,
but nothing else.

When a user creates a task, the audience is already there (group name).

On 1/2/07, Boris Mann <boris at bryght.com> wrote:
>
> On 1/2/07, Khalid B <kb at 2bits.com> wrote:
> > I am also playing with casetracker, CCK (for node types), and og (for
> > separating
> > each project/client).
> >
> > So far it is promising for sure, but can't give it more time in the
> upcoming
> > weeks.
>
> So....I looked at this (casetracker + OG), and there seem to be some
> problems unless I am missing something. Let me walk through the recipe
> and where I ran into issues (from memory, and the site is since
> reconfigured):
> * set OG settings to OG-enable project nodes (casetracker_basic or
> whatever it's called)
> * control cases (+ pages, stories, image, etc. etc. as needed) with OG
> * create project == creating a group (no problem)
> * subscribe users as needed to the group
>
> Problem: associating a case with a project doesn't protect it -- you
> need to select the project AND the "audience", which is a duplicate of
> the projects (just the OG access control).
>
> Problem (same with all OG, of course): need to manually subscribe all
> people that need access to each project.
>
> Ideally, OG enabled project nodes would have cases automagically
> access controlled with the parent projects OG...blah...that was as
> hard to say as it is to do.
>
> I ended up implementing this with tac_lite and casetracker: both cases
> and projects are assigned to role access categories, and it seems
> simpler. When creating new projects or cases, visibility is tied to
> one category which gives access to everyone that needs it in one fell
> swoop. Also, you can have "more private" cases (e.g. your dev team can
> post stuff in a customer project without exposing it) easier.
>
> And, of course, there is email notification from both casetracker and OG.
>
> Hope that provides some interesting feedback,
>
> --
> Boris Mann
> Vancouver 778-896-2747
> San Francisco 415-367-3595
> Skype borismann
> http://www.bryght.com
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20070102/7d9b71de/attachment.htm