[Rt-commit] rt branch, 4.0-trunk, updated. rt-4.0.2-38-g464e3ae

[Thomas Sibley]

The branch, 4.0-trunk has been updated
       via  464e3aea37b4c59d442cd10bc65ed20c3bd7fd72 (commit)
      from  3a0b446e7a3623a25e6f87d59964aa2d48331424 (commit)

Summary of changes:
 etc/RT_Config.pm.in |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

- Log -----------------------------------------------------------------
commit 464e3aea37b4c59d442cd10bc65ed20c3bd7fd72
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Tue Aug 30 09:33:43 2011 -0400

    Clarify that a lifecycles mapping is required even when statuses are the same

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index f98a4cc..869375e 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -2229,7 +2229,8 @@ For example:
 
 Unless there is an explicit mapping between statuses in two different
 lifecycles, you can not move tickets between queues with these
-lifecycles.  Such a mapping is defined as follows:
+lifecycles.  This is true even if the different lifecycles use the exact
+same set of statuses.  Such a mapping is defined as follows:
 
     __maps__ => {
         'from lifecycle -> to lifecycle' => {

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