You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2013/02/20 19:57:48 UTC

[Apache Bloodhound] #408: Implement permission schemes (templates) for multiproduct environments

#408: Implement permission schemes (templates) for multiproduct environments
--------------------------------------+--------------------
 Reporter:  matevzb                   |      Owner:  nobody
     Type:  enhancement               |     Status:  new
 Priority:  major                     |  Milestone:
Component:  multiproduct              |    Version:
 Keywords:  multiproduct permissions  |
--------------------------------------+--------------------
 Currently the multiproduct implementation copies the default trac's
 permissions into each newly created product. These permissions then have
 to be manually edited for each product which is a tedious and cumbersome
 task when dealing with lots of products.
 Permission schemes/templates would enable users to define and save sets of
 permissions which could then be applied to a single or multiple products
 in one step.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/408>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Re: [Apache Bloodhound] #408: Implement permission schemes (templates) for multiproduct environments

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#408: Implement permission schemes (templates) for multiproduct environments
---------------------------+--------------------------------------
  Reporter:  matevzb       |      Owner:  nobody
      Type:  enhancement   |     Status:  new
  Priority:  major         |  Milestone:
 Component:  multiproduct  |    Version:
Resolution:                |   Keywords:  multiproduct permissions
---------------------------+--------------------------------------
Description changed by olemis:

Old description:

> Currently the multiproduct implementation copies the default trac's
> permissions into each newly created product. These permissions then have
> to be manually edited for each product which is a tedious and cumbersome
> task when dealing with lots of products.
> Permission schemes/templates would enable users to define and save sets
> of permissions which could then be applied to a single or multiple
> products in one step.

New description:

 Currently the multiproduct implementation copies the default trac's
 permissions into each newly created product. These permissions then have
 to be manually edited for each product which is a tedious and cumbersome
 task when dealing with lots of products.

 Permission schemes/templates would enable trac admins to define and save
 sets of permissions which product owners / admins could then apply to a
 single or multiple products in one step.

--

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/408#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker