Changes between Version 18 and Version 19 of SensitiveTicketsPlugin
- Feb 21, 2012, 6:52:28 AM (3 years ago)
v18 v19 34 34 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`. 35 35 36 This plugin also adds the REDACTED_SENSITIVE_ACTIVITY_VIEW 37 permission. Accounts with this permission will be able to see 38 activity on sensitive material in the timeline, but will only be 39 able to identify it by ticket number, comment number, and 40 timestamp. 36 This plugin also adds the SENSITIVE_ACTIVITY_VIEW permission, 37 which is narrower in scope than SENSITIVE_VIEW. Accounts with 38 SENSITIVE_ACTIVITY_VIEW will be able to see activity on sensitive 39 material in the timeline, but will only be able to identify it by 40 ticket number, comment number, and timestamp. All other content 41 will be redacted. 41 42 42 REDACTED_SENSITIVE_ACTIVITY_VIEW can be useful (for example) for 43 SENSITIVE_ACTIVITY_VIEW can be useful (for example) for 43 44 providing a notification daemon the ability to tell that some 44 45 activity happened without leaking the content of that activity.