Changes between Version 31 and Version 32 of SensitiveTicketsPlugin

Timestamp:

Oct 17, 2017, 4:34:52 PM (7 years ago)

Author:

figaro

Comment:

Further cosmetic changes

SensitiveTicketsPlugin

@@ -9 +9 @@
 '''Scenario 1'''
 
-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 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 and the vulnerability is hidden to all other users.
 
 '''Scenario 2'''
 
-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.
+A team uses Trac to handle its business development tasks, but wants to leave the record open for all. Some tasks, however, are sensitive, for example dealing with difficult clients or prospective clients where negotiations on budgets are still ongoing. Those tickets are marked as sensitive and hidden to others, but viewable by the business development team.
 
 '''Beware''':
@@ -69 +69 @@
 `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.
+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].
 
 == Recent Changes