Changes between Initial Version and Version 1 of AnnouncerPlugin/Concerns


Ignore:
Timestamp:
Jan 7, 2008, 8:28:15 AM (16 years ago)
Author:
Stephen Hansen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AnnouncerPlugin/Concerns

    v1 v1  
     1 * Email Addresses
     2  * Keeping the ability to anonymously subscribe to a ticket is important; any validation?
     3  * Optional verification? This would require sending a message asking the person if they can receive mails, and until they say yes, never sending the notices. An external module to 'get' email would be required.
     4  * Be sure apostrophes in names work okay.
     5  * Should be able to plug-into an email address discovery system; e.g. if 'bob' is authenticated, get their address.
     6   * It may be sufficient to add an '@address.com' to the end of an authenticated user in the case of an intranet, but not always. As figuring this out may be slightly complicated, the delivery system should perhaps allow a pluggable
     7  * Allow multiple email addresses per user?
     8 * Delivery
     9  * Use a subprocess to prevent blocking and not require threads.
     10  * Test plain text format mailing for proportional font
     11  * Add some X-Trac-* headers for filtering perhaps?
     12  * Email URL syntax: Ticket URL: <URL:http://developer.pidgin.im/ticket/1428#comment:2>
     13  * Allow for an email's Sender field to specify the user who made the change?
     14  * A /usr/bin/sendmail IAnnouncementDelivererererer module.
     15 * Tickets
     16  * Change notices should use the label, not the field name, for custom fields.
     17  * trac:6306
     18  * Per-ticket watching beyond the subscription rule-system; e.g. in the ticket view one can click "Watch Me" with various options. "New comments", "status changed"... etc.
     19  * Send notification when a file is attached?
     20   * Include link to the attachment.
     21  * Filter not just on 'prop changed', but on /certain/ props. Perhaps, "all, changed=field"
     22  * Filter on component owner.
     23  * Filter on "changed by..." E.g., self, vs others.
     24  * A "trivial change" notice? Let users filter on "non-trivial"
     25 * A Mailing List-type subscription? E.g., a list of users can receive a message on a new release? Notably would require an IMilestoneChangeListener.
     26 * Wiki
     27  * Notify on change, delete, (rename?)
     28  * Notify on attachment add
     29 * Milestone
     30  * Notification on set-date, change-text, completion
     31
     32Consider trac:5670 -- ???