Changes between Version 1 and Version 2 of TicketAccessPlugin


Ignore:
Timestamp:
Jun 14, 2011 12:44:45 PM (3 years ago)
Author:
solarwind
Comment:

modify example

Legend:

Unmodified
Added
Removed
Modified
  • TicketAccessPlugin

    v1 v2  
    2525== Example == 
    2626 
    27 For example I have some users which I have assigned to 2 groups 
    28 grpA 
    29   user1 
    30   user2 
     27For example I have some users which I have assigned to 3 groups 
    3128 
    32 grpB 
    33   user1 
    34   user3 
     29|| '''grpA''' || '''grpB''' || '''grpC''' || 
     30||  user1   ||  user1  ||  user4  || 
     31||  user2   ||  user3  ||  user5  || 
    3532 
    36 grpC 
    37   user4 
    38   user5 
    3933 
    40 A user can belong to more than a group. So the ticket view, I have created an additional field to enter a comma delimited list of groups I should restrict access to the ticket.  
     34A user can belong to more than a group. In the ticket view, I have created an additional field to enter a comma delimited list of groups I should restrict access to the ticket.  
    4135 
    42 For example when I am creating a new ticket, I decide that grpA and grpC should be restricted from viewing the ticket. I just enter a comma delimited list of groups I should restrict 
     36For example when I am creating a new ticket, I decide that grpA and grpC should be restricted from viewing the ticket. I just enter a comma delimited list of groups I should restrict. This is shown in the image below 
    4337 
    44 grpA, grpC 
     38[[Image(create-ticket-view.png)]] 
    4539 
    46 And then the ticket will be hidden from users in these 2 groups. In our example, only users from grpB are allowed to see the ticket. However user1 has already been restricted due to him belonging to grpA, so in effect, only user3 has access to the ticket 
     40And then the ticket will be hidden from users in these 2 groups.  
     41 
     42In our example, only users from grpB (user1 and user3) are allowed to see the ticket. However user1 has already been restricted due to him belonging to grpA, so in effect, only user3 has access to the ticket 
     43 
     44Note that if a user has TRAC_ADMIN permissions then he will be allowed full access regardless of the restrictions imposed by the plugin 
    4745 
    4846== Recent Changes ==