Changes between Version 27 and Version 28 of WorkflowNotificationPlugin
- Timestamp:
- Mar 26, 2022, 8:36:59 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WorkflowNotificationPlugin
v27 v28 7 7 This plugin enables flexible configuration of email notifications tied to ticket workflow changes. 8 8 9 Administrators can configure any number of distinct email notifications to be sent out when a workflow operation occurs on a ticket. Each email notification is specifically attached to one or more workflow operations, so (for example)separate emails can be sent out when a ticket is accepted, reassigned, resolved, reopened, or marked "in QA".9 Administrators can configure any number of email notifications to be sent out when a workflow operation occurs on a ticket. Each email notification is specifically attached to one or more workflow operations, so for example separate emails can be sent out when a ticket is accepted, reassigned, resolved, reopened, or marked "in QA". 10 10 11 11 Each email notification's subject, body, and recipients are fully configurable by administrators, as Genshi templates which have access to the ticket's data, the comment (if any) that was left on the ticket, and the author of the change. Therefore notifications can be very flexible: some notifications can be sent to the ticket's reporter, others to its owner or CC list, others to the current updater, and others to hard-coded lists of users. … … 13 13 The notification emails sent by this plugin respect Trac's `ALWAYS_CC` and `ALWAYS_BCC` settings. 14 14 15 The notification emails sent by this plugin are independent of Trac's `ALWAYS_NOTIFY_UPDATER`, `ALWAYS_NOTIFY_OWNER` and `ALWAYS_NOTIFY_REPORTER` 16 settings. Trac's built-in email notifications will be sent according to those settings, independent of this plugin's emails. 15 The notification emails sent by this plugin are independent of Trac's `ALWAYS_NOTIFY_UPDATER`, `ALWAYS_NOTIFY_OWNER` and `ALWAYS_NOTIFY_REPORTER` settings. Trac's built-in email notifications will be sent according to those settings, independent of this plugin's emails. 17 16 18 17 == Bugs/Feature Requests … … 55 54 Now you just need to configure some notifications, see below for details and examples. 56 55 57 == Example58 59 === Configuration60 61 Configure one or more notification emails attached to workflow events using a `ticket-workflow-notifications` section in `trac.ini`. 56 == Configuration 57 58 === General configuration 59 60 Configure one or more notification emails attached to workflow events using a `ticket-workflow-notifications` section in `trac.ini`. See the [trac:wiki:TracDev/DataModels#Ticket Trac documentation] for information on the available attributes of the `Ticket` object. 62 61 63 62 Within this section, each entry is a notification email that may be sent out for a ticket. Here is an example: … … 117 116 === Notifications for new tickets 118 117 119 Most notifications are configured to refer to one or more workflow actions, like accept, leave, reassign, resolve, etc.118 Most notifications are configured to refer to one or more workflow actions, like `accept`, `leave`, `reassign`, `resolve`, etc. 120 119 121 120 You can also configure notifications to be triggered when a ticket is newly created. To do this, use the special workflow action `@created` like so: … … 182 181 183 182 Meanwhile, if there are any newlines whatsoever in your `.subject` configuration, the plugin will replace them with spaces. This ensures that your email will have a valid subject (email subjects cannot contain newlines). 184 185 183 186 184 === Emailing all commenters on a ticket … … 201 199 }}} 202 200 203 Or you can email everyone who has ever participated on the ticket at all:201 Or you can email everyone who has ever participated on the ticket: 204 202 {{{#!ini 205 203 [ticket-workflow-notifications] … … 221 219 222 220 Check the project's Github page for recent changes: https://github.com/trac-hacks/trac-WorkflowNotificationPlugin 223 224 221 225 222 == Author/Contributors