Changes between Version 8 and Version 9 of TicketAccessPlugin


Ignore:
Timestamp:
Mar 10, 2015, 7:09:59 PM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes, tagged with license

Legend:

Unmodified
Added
Removed
Modified

  • TicketAccessPlugin

    v8 v9  
    11[[PageOutline(2-5,Contents,pullout)]]
    22
    3 = TicketAccessPlugin =
     3= Restrict access rights for tickets based on user's group
    44
    5 == Description ==
     5== Description
    66
    7 Restrict access rights for tickets based on user's group. This plugin was modified from the SensitiveTicketsPlugin.
     7This plugin restricts the user's access rights for tickets depending on the group the user belongs to. This plugin was modified from the SensitiveTicketsPlugin.
    88
    9 == Bugs/Feature Requests ==
     9== Bugs/Feature Requests
    1010
    1111Existing bugs and feature requests for TicketAccessPlugin are
    … …  
    1515[http://trac-hacks.org/newticket?component=TicketAccessPlugin&owner=solarwind new ticket].
    1616
    17 == Download ==
     17== Download
    1818
    1919Download the zipped source from [https://sourceforge.net/projects/ticketaccess/files/ here].
    2020
    21 == Source ==
     21== Source
    2222
    2323You can browse TicketAccessPlugin from [svn://svn.code.sf.net/p/ticketaccess/code-0 here]
    2424
    25 == Installation ==
    26 After downloading and installing, you will need to enable it in the trac admin page.
    27 You will have to do a database upgrade of your trac.
     25== Installation
    2826
    29 Changes are also needed in the trac.ini file
     27After downloading and installing, you will need to enable it in the Trac admin page.
     28You will have to do an upgrade of your Trac database.
    3029
    31 Under the trac subsection, please add the permission policy '!TicketAccessPolicy' to the beginning of the permission_policies item
     30Changes are also needed in the `trac.ini` file:
    3231
    33 [trac][[br]]
    34 ...[[br]]
    35 permission_policies = '''!TicketAccessPolicy''', !DefaultPermissionPolicy, !LegacyAttachmentPolicy[[br]]
     32Under the `trac` subsection, please add the permission policy '!TicketAccessPolicy' to the beginning of the permission_policies item:
     33
     34{{{
     35#!ini
     36[trac]
     37permission_policies = '''!TicketAccessPolicy'''
    3638...
     39}}}
    3740
    38 Thereafter when you create a ticket, there will be new textfield to key in the users you want to restrict from accessing the ticket.
     41Thereafter when you create a ticket, there will be a new textfield to key in the users you want to restrict from accessing the ticket.
    3942
    40 == Example ==
     43== Example
    4144
    42 For example I have some users which I have assigned to 3 groups
     45For example, suppose there some users which have been assigned to 3 groups:
    4346
    4447|| '''grpA''' || '''grpB''' || '''grpC''' ||
    … …  
    4750
    4851
    49 A 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.
     52A user can belong to more than one 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.
    5053
    51 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. This is shown in the image below
     54For example when creating a new ticket, I may decide that grpA and grpC should be restricted from viewing the ticket. In that case, just enter a comma delimited list of groups that require access to be restricted:
    5255
    5356[[Image(create-ticket-view.png)]]
    … …  
    5558And then the ticket will be hidden from users in these 2 groups.
    5659
    57 In 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
     60In 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.
    5861
    59 Note that if a user has TRAC_ADMIN permissions then he will be allowed full access regardless of the restrictions imposed by the plugin
     62Note that if a user has TRAC_ADMIN permissions then he will be allowed full access regardless of the restrictions imposed by the plugin.
    6063
    61 
    62 == Author/Contributors ==
     64== Author/Contributors
    6365
    6466'''Author:''' [wiki:solarwind75] [[BR]]
    65 '''Maintainer:''' [wiki:solarwind75] [[BR]]
     67'''Maintainer:''' [[Maintainer]] [[BR]]
    6668'''Contributors:'''