[Rt-commit] rt branch, 4.0/status-of-created-reminders, updated. rt-4.0.13-50-gfbbd36d

[Thomas Sibley]

The branch, 4.0/status-of-created-reminders has been updated
       via  fbbd36dba9885920dd2f221c222c3e04b245d41f (commit)
      from  a9034026f9a20d00520239a87caccc405ea1a70e (commit)

Summary of changes:
 docs/UPGRADING-4.0 | 11 +++++++++++
 1 file changed, 11 insertions(+)

- Log -----------------------------------------------------------------
commit fbbd36dba9885920dd2f221c222c3e04b245d41f
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Fri Jun 14 13:05:52 2013 -0700

    Add an upgrade note about reminder statuses

diff --git a/docs/UPGRADING-4.0 b/docs/UPGRADING-4.0
index 687dfbc..ef31813 100644
--- a/docs/UPGRADING-4.0
+++ b/docs/UPGRADING-4.0
@@ -189,3 +189,14 @@ these types before insertion.
 
 Site-specific custom types (anything but ticket, reminder or approval)
 are not affected by these changes.
+
+=head1 UPGRADING FROM 4.0.13 AND EARLIER
+
+=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.

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