Component permissions (how to set per-user visibility in dropdown lists?)

[d@vid seaward]

Hello all,

Beginner Trac user here. We want to run multiple projects on a single
environment, with similar outcomes to the one described in the old
query below (the requirement to hide tickets etc from multiple users)
and I looked at the PrivateTickets plugin as suggested. Our plan is to
make user groups owners of tickets, and thereby hide/show tickets from
groups of users. (This is a feature of PrivateTickets.)

However, all component and milestone values will be visible to all
users (e.g. when creating a ticket). We also want to show/hide
dropdown information per user (i.e. users/groups are restricted to
which component and milestones values they can see in a dropdown). Are
there any existing plugins that make visible dropdown values user-
dependent?

Alternatively, is there any other way to run multiple projects on one
environment, and restrict access to dropdown values at the same time?
(Is this what 0.11 fine-grained permissions are supposed to be giving
us? - once they are extended to tickets in addition to the already-
existing permissions on SVN and wiki)

d@vid

References:

* http://trac-hacks.org/wiki/PrivateTicketsPlugin (plugin restricting
access based on owner/cc field)

* http://trac-hacks.org/ticket/2068 (an alternate solution with no
suggestions)

* http://trac.edgewall.org/wiki/TracDev/SecurityBranch and
http://trac.edgewall.org/browser/trunk/sample-plugins/authz_policy.py
(just in case anyone else is looking for a similar solution - this
applies wiki permissions only, not ticket-based permissions/access/
filtering)

Old group message "Groups and permissions":
On Dec 29 2006, 6:22 am, Noah Kantrowitz <kan...@rpi.edu> wrote:
> Look at the PrivateTickets plugin on trac-hacks.
>
> --Noah
>
> On Dec 28, 2006, at 7:40 PM, Lincoln Mongillo wrote:
>
>
>
>
>
> > I'm starting to use trac quite a bit for a specificprojectthat
> > involves multiple vendors. Because myprojecthas various vendors,
> > and due to security\nda issues outside of my hands, I want to keep one
> > vendor from looking at tickets\milestones from another vendor. Is
> > that possible with Add Subject to Group or GrantPermissionsin the
> > admin section?
>
> > cheers,

[Noah Kantrowitz]

HideVals is somewhat of a companion to PrivateTickets that provides this
functionality.

--Noah

> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "Trac Users" group.
> To post to this group, send email to trac-...@googlegroups.com
> To unsubscribe from this group, send email to trac-users-...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
>

[d@vid seaward]

Hi Noah,

Thanks for the pointer, I don't know how I missed HideVals in my
search through the Trac Hacks list! This really looks like a killer
combination for running customer-facing projects in a single
environment.

I've seen elsewhere that you are waiting for 0.11 security to
stabilise before converting these plugins, so we're going to rethink
how to move forward on this (we're running 0.11dev). But thanks again!

d@vid

> > *http://trac-hacks.org/wiki/PrivateTicketsPlugin(plugin restricting

> > access based on owner/cc field)
>

> > *http://trac-hacks.org/ticket/2068(an alternate solution with no