[Rt-commit] rt branch, 4.0-trunk, updated. rt-4.0.13-76-g147b941

[Alex Vandiver]

The branch, 4.0-trunk has been updated
       via  147b941122c888b5e4474db5473992c174d2a957 (commit)
       via  fbbd36dba9885920dd2f221c222c3e04b245d41f (commit)
       via  a9034026f9a20d00520239a87caccc405ea1a70e (commit)
      from  82aa6ab5b62ddbeb78067b5be3c37259370b9b5d (commit)

Summary of changes:
 docs/UPGRADING-4.0  | 11 +++++++++++
 lib/RT/Reminders.pm |  1 +
 t/web/reminders.t   |  8 ++++----
 3 files changed, 16 insertions(+), 4 deletions(-)

- Log -----------------------------------------------------------------
commit 147b941122c888b5e4474db5473992c174d2a957
Merge: 82aa6ab fbbd36d
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Fri Jun 14 16:27:51 2013 -0400

    Merge branch '4.0/status-of-created-reminders' into 4.0-trunk
    
    Conflicts:
    	docs/UPGRADING-4.0

diff --cc docs/UPGRADING-4.0
index 9bca8f1,ef31813..59e5db4
--- a/docs/UPGRADING-4.0
+++ b/docs/UPGRADING-4.0
@@@ -192,16 -192,11 +192,27 @@@ are not affected by these changes
  
  =head1 UPGRADING FROM 4.0.13 AND EARLIER
  
++=head2 Outgoing mail From: header
++
 +The "Default" key of the C<$OverrideOutgoingMailFrom> config option now,
 +as previously documented, only applies when no ticket is involved.
 +Previously it was also used when a ticket was involved but the
 +associated queue had no specific correspond address.  In such cases the
 +global correspond address is now used.
 +
 +The config option C<$SetOutgoingMailFrom> now accepts an email address
 +as a value which will act as a global default.  This covers the simple
 +case of sending all bounces to a specific address, without the previous
 +solution of resorting to defining all queues in
 +$OverrideOutgoingMailFrom.  Any definitions in the Override option
 +(including Default) still take precedence.  See
 +L<RT_Config/$SetOutgoingMailFrom> for more information.
++
+ =head2 Reminder statuses
+ 
+ New reminders are now created in the "reminder_on_open" status defined in your
+ lifecycles.  For the default lifecycle, this means reminders will start as
+ "open" instead of "new".  This change is for consistency when a completed
+ reminder is reopened at a later date.  If you use custom lifecycles and added
+ further transition restrictions, you may need to adjust the L<"reminder_on_open"
+ setting|RT_Config/reminder_on_open> in your lifecycles.

-----------------------------------------------------------------------