Version 22 (modified by Ryan J Ollos, 5 years ago) (diff)

Added page outline.


Hide sensitive tickets with a checkbox.


SensitiveTickets is a plugin that lets users mark tickets as "sensitive" with a checkbox on the ticket form. Sensitive tickets are viewable only to those with the SENSITIVE_VIEW permission.

Beware: Hooks that send mail on ticket changes will still send mail for sensitive tickets; this may not be what you want.

Beware: if the plugin is removed, disabled, or fails to load, trac will opt to display sensitive tickets ("failing open" instead of "failing closed")

This plugin is supported on trac 0.11.6 or higher.


A user submits a security related ticket to a project's Trac, which is generally open to the public. They mark it as "Sensitive" so that only people in the internal team that deal with security issues can see the ticket.

A team uses Trac to handle its business development tasks, but wants to leave the record open for all. Some tasks, however--say, dealing with difficult clients--are sensitive. Those tickets are marked as sensitive and hidden to others but viewable by the business development team.


The plugin is based on the example but uses a checkbox instead of text in the summary or keywords to mark a ticket as sensitive.

See also: PrivateTicketsPlugin.


Once this plugin is enabled, you'll have to insert it at the appropriate place in your list of permission policies, e.g.

permission_policies = SensitiveTicketsPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy

Users with SENSITIVE_VIEW privileges will be able to see and act on tickets marked sensitive, as will any user configured to be able to bypass the sensitive marker (e.g. if the user is the ticket owner or reporter, or is in the CC field, and the associated flags are set in [sensitivetickets] section of trac.ini.

This plugin also adds the SENSITIVE_ACTIVITY_VIEW permission, which is narrower in scope than SENSITIVE_VIEW. Accounts with SENSITIVE_ACTIVITY_VIEW will be able to see activity on sensitive material in the timeline, but will only be able to identify it by ticket number, comment number, and timestamp. All other content will be redacted. SENSITIVE_ACTIVITY_VIEW can be useful (for example) for providing a notification daemon the ability to tell that some activity happened without leaking the content of that activity.

Needs an environment upgrade (or just adding the appropriate stanza to [ticket-custom] in trac.ini after enabling.

Bugs/Feature Requests

Existing bugs and feature requests for SensitiveTicketsPlugin are here.

If you have any issues, create a new ticket.

Source & Download

You can check out SensitiveTicketsPlugin from here using Subversion, or browse the source with Trac.

Download the zipped source from [download:sensitiveticketsplugin here].

Recent Changes

16892 by rjollos on 2017-10-16 23:59:38
TracSensitiveTickets 1.2.3dev: Bump version

TracSensitiveTickets 1.2.2 has been published to PyPI.

Refs #13297.

16891 by rjollos on 2017-10-16 23:58:02
TracSensitiveTickets 1.2.2dev: Fix failure with non-integer resource id

Refs #13297.

16890 by rjollos on 2017-10-16 23:46:46
sensitivetickets 0.24: Fix failure with non-integer resource id

Restore the 0.11 directory to the revision prior to
r11289, which should be compatible with Trac 0.11.6.

Refs #13297.



Authors: sbenthall, dkgdkg
Maintainer: dkgdkg
Contributors: k0s, obs