Changes between Version 32 and Version 33 of SensitiveTicketsPlugin


Ignore:
Timestamp:
Oct 17, 2017, 5:36:07 PM (4 years ago)
Author:
Ryan J Ollos
Comment:

Don't suggest manually editing ticket-custom section.

Legend:

Unmodified
Added
Removed
Modified
  • SensitiveTicketsPlugin

    v32 v33  
    6363}}}
    6464
    65 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. For example, his happens in the case 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`.
     65Users 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. For example, this happens in the case 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`.
    6666
    6767This 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.
     
    6969`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.
    7070
    71 After installation the Trac project needs an environment upgrade or just adding the appropriate stanza to `[ticket-custom]` in `trac.ini` after enabling. For the latter, see [t:TracTicketsCustomFields].
     71After installation the Trac project needs an environment upgrade.
    7272
    7373== Recent Changes