|Version 16 (modified by obs, 7 years ago) (diff)|
Various hacks to alter Ticket form behaviour and Ticket Permissions
An issue has been found and fixed where users viewing custom reports could see the value of ticket fields that should be hidden, everyone should update.
Nearly christmas! I've added the ability to deny access to ticket types by permission. All known bugs are fixed.
I have adopted this hack and will be going through the tickets bugs first, if you wish to request any new features or report bugs please do. ~Obs
Trac in 0.11 provided us with this incredibly powerful and terrible bit of dark power -- the ability to apply Genshi Transformers to the templates before they hit the user. The power is awesome; and with this plugin I have abused that power for evil purposes.
And there are plans for more evil in the future!
Basically, the plugin adds the ability to tweak any of the Ticket fields-- be they custom or standard-- in the following ways:
- disable - The field won't be editable.
- hide - The field will simply be invisible.
- label - Rename a field... in particular one of the built-in fields.
- notice - Add a small notice below a field.
- tip - Provide a pretty java-script tooltip when the control overs over the field. (Useful, for example, to give people a reminder for the difference between 'priority' and 'severity'
- permission - Set a permission that is required to edit that specific field. This is particularly useful in an environment where you let users set severity-- so they need TICKET_CHGPROP-- but you only want certain people to be able to edit the Priority.
The plugin also lets you define arbitrary permissions, say, MASTER_OF_PRIORITIES, if you want to require someone to have such a custom permission to edit a certain field.
The plugin can also deny access to certain ticket types by permissions using the ticket_type ini setting.
If you have any issues, create a new ticket please cc yourself if you're anonymous or you won't be notified of when I respond!
Installation and Configuration
Latest Trac 0.11
- Download the zipped source from [download:blackmagictickettweaksplugin here].
- You can check out BlackMagicTicketTweaksPlugin using Subversion, or browse the source with Trac.
The easiest way to install the BlackMagicTicketTweaksPlugin is to simply point easy_install at the t-h.o SVN repository, a la:
Alternatively, you may download the source and go into the 0.11 directory and then run:
python setup.py install
After you have installed the BlackMagicTicketTweaksPlugin, you must enable it. You can do so in the Administration panel of Trac, or in trac.ini by adding:
[components] blackmagic.* = enabled
Any fields that you would like to tweak with this plugin must be listed in the tweaks option of the [blackmagic] section in your TracIni. This list is comma-separated and lower case. For example:
[blackmagic] tweaks = cc, priority, severity
Next you must specify all the actions that you want performed on those fields. You may have as many actions as you'd like.
The actions are specified as <field>.<action> = <value>
[blackmagic] tweaks = priority priority.permission = TRAC_ADMIN
The following are considered True settings in trac.ini:
They are all case insensitive
The following actions are supported:
- If True, the field will be present and its value shown but it won't be editable. By default the label will be striked out, but if you set the gray_disabled option to some value, that color will be used instead. Suggested value is something like #cccccc
- If True, the field will be completely removed and so not settable and invisible.
- The label for the field will be renamed to this value. Not terribly useful for the custom fields, but it lets you adjust the default fields names.
- Adds a small notice under the field; useful for little notes about the field.
- A comma-separated list of permissions that the user must have at least one of to edit this field. If they do not, the field will be disabled (as above). This allows per-field permissions.
- This only means something on a field with a permission action set. In this case, it determines how to handle if the user has no such permission. Valid options are either 'disable' (default) or 'hide', both treated as if the field had such an action set as above.
You may create new permissions in Trac for use above (or anywhere you'd like, really) by specifying the permission option, as in:
[blackmagic] permissions = TICKET_CHG_PRIORITY, TICKET_CHG_CC
To deny access to a ticket type by permission use the following options
ticket_type.* = PERMISSION (replacing * with the ticket type, i.e. defect) I.e. to only allow users with the TICKET_MODIFY permission access to defect tickets you would set the following
[blackmagic] ticket_type.defect = TICKET_MODIFY
Denying access to a ticket type will prevent users from seeing them in reports, viewing the tickets of that type and creating tickets of that type.
Currently the ticket_type.* option can only hold one permission, if you want a comma separated list raise a ticket and request it.
To use this option you will need to add BlackMagicTicketTweaks to the permission_policies option in the [trac] section of the trac.ini i.e.
[trac] permission_policies = BlackMagicTicketTweaks, DefaultPermissionPolicy
[blackmagic] permissions = MASTER_OF_PERMISSIONS, TICKET_RAISE_DEFECT tweaks = severity, priority priority.tip = The priority is the Project-defined importance of the issue, and in general the order in which things will tend to be done. severity.tip = The severity is how important this issue is to the customer or you. priority.permission = MASTER_OF_PERMISSIONS ticket_type.defect = TICKET_RAISE_DEFECT ticket_type.task = TICKET_ADMIN
- 13913 by rjollos on 2014-05-09 18:22:45
Removed debugging print statement from . Refs #11740.
- 13817 by rjollos on 2014-04-07 08:09:38
0.12.2: Removed empty CSS directory.
- 13734 by rjollos on 2014-03-12 03:26:06
0.11.2 / 0.12.2: Move class attributes to instance attributes, to avoid reported issues with shared state between Trac environments. Fixes #7872.