[Rt-commit] rt branch, 4.0/document-seecustomfield-upgrade, created. rt-4.0.11-65-g72449ca

[Thomas Sibley]

The branch, 4.0/document-seecustomfield-upgrade has been created
        at  72449cac0140de4ac370ccfb0565b4e7a74a8965 (commit)

- Log -----------------------------------------------------------------
commit 72449cac0140de4ac370ccfb0565b4e7a74a8965
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Mon Apr 22 13:50:33 2013 -0700

    Document the need to grant SeeCustomField manually during the upgrade to 3.4
    
    SeeCustomField was added by f8b1925 in 3.3.2 but no automatic upgrade
    step or documentation was ever added.

diff --git a/docs/UPGRADING-3.4 b/docs/UPGRADING-3.4
index 89454bd..2043582 100644
--- a/docs/UPGRADING-3.4
+++ b/docs/UPGRADING-3.4
@@ -9,3 +9,10 @@ changed to "ModifyCustomField"
 Custom Fields now have an additional right, "ModifyCustomField".  This right
 governs whether a user can modify an object's custom field values for a
 particular custom field. This includes adding, deleting and changing values.
+
+=head1 UPGRADING FROM 3.3.2 AND EARLIER
+
+Viewing custom fields now requires the "SeeCustomField" right either globally
+or on a per-queue basis.  Global CFs are no longer visible to everyone and
+SeeQueue is no longer sufficient to view queue-level CFs.  You must grant the
+"SeeCustomField" right manually after upgrade.

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