Edgewall Software

Changes between Initial Version and Version 1 of Ticket #8395


Ignore:
Timestamp:
Jun 17, 2009, 5:21:49 PM (15 years ago)
Author:
Christian Boos
Comment:

Replying to xyanipheia:

… maybe this approach may be implemented earlier than milestone 2.0 for #8294?

Well, this mainly depends of someone implementing that feature, see TracDev/SubmittingPatches.

As here it's mainly a matter of adding a boolean config option and checking for the flag before writing the content of the notification mail, this should be a pretty easy task. See TracNotification to get some ideas about the config option name. I'd suggest ticket_omit_content, or if you want more control, ticket_omit_fields, ticket_omit_changes and ticket_omit_comment. All defaulting to False for compatibility with current behavior.

Also the already ticket_subject_template can be used to restrict the information shown in the mail summary.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #8395

    • Property Keywords confidentiality added
    • Property Milestone → 0.13

  • Ticket #8395 – Description

    initial v1  
    1 In #8294 GPG encoded notifications were mentioned. An easy workaround is to restrict the content of notifications. In this case no critical content is sent to the recipients, only a ticket number and the project link. Of course, encrypted notification is more preferable, but maybe this approach may be implemented earlier than milestone 2.0 für #8294?
     1In #8294 GPG encoded notifications were mentioned. An easy workaround is to restrict the content of notifications. In this case no critical content is sent to the recipients, only a ticket number and the project link. Of course, encrypted notification is more preferable, but maybe this approach may be implemented earlier than milestone 2.0 for #8294?
    22This approach allows to use TRAC in restricted environments if additionally:
    33 * the server is protected (https with client certificates, ...