[Rt-commit] rt branch, 4.4/use-status-active, updated. rt-4.4.0-62-g23b3da2

[Jim Brandt]

The branch, 4.4/use-status-active has been updated
       via  23b3da2d47256daa60f116b4d87f9688b2523ec1 (commit)
      from  6ebcea11dc5629403c116fc090d5096c6c17d283 (commit)

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

- Log -----------------------------------------------------------------
commit 23b3da2d47256daa60f116b4d87f9688b2523ec1
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Mon May 16 09:33:40 2016 -0400

    Note the __Active__ option for RT's saved searches
    
    6ebcea11d updates initialdata for new RT's to now use the
    __Active__ placeholder for RT's saved searches to handle
    custom lifecycles. Add a note to the UPGRADING file for
    users to upgrade existing instances if they have
    custom lifecycles.

diff --git a/docs/UPGRADING-4.4 b/docs/UPGRADING-4.4
index f19c493..6aeff46 100644
--- a/docs/UPGRADING-4.4
+++ b/docs/UPGRADING-4.4
@@ -261,6 +261,17 @@ Now you can simply write:
 
 =item *
 
+We updated default RT searches that previously specified 'new' and 'open' status
+to use the new '__Active__' and '__Inactive__' syntax where appropriate. For new
+RT's, this means the default RT at a Glance searches will now work with custom
+lifecycles without updating these searches.
+
+For existing RTs, you may want to update the "highest priority tickets I own" and
+'newest unowned tickets' system searches to use '__Active__' rather than specific
+statuses if you have a custom lifecycle.
+
+=item *
+
 We added an "Entry Hint" to custom fields. Previously, we used the custom
 field's C<FriendlyType> as its hint, but now it is replaced by the per-CF
 customizable C<EntryHint> field.

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