[Rt-commit] [rtir] 01/01: More docs about SLA CF

[Kevin Falcone]

This is an automated email from the git hooks/post-receive script.

falcone pushed a commit to branch 3.0-trunk
in repository rtir.

commit 7d4ef12d28f3976ef3b8e0164b778032333083b9
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Fri Oct 3 17:49:31 2014 -0400

    More docs about SLA CF
    
    a1b70753 fixed the SLA part of UPGRADING-3.0 but did so in a way likely
    to be missed by users upgrading from 3.0.2.  Add a specific 3.0.3
    upgrading note.  Additionally, further document how to remove the CF and
    that new installs of RITR 3.0 are unaffected.
---
 docs/UPGRADING-3.0 | 24 +++++++++++++++++++-----
 1 file changed, 19 insertions(+), 5 deletions(-)

diff --git a/docs/UPGRADING-3.0 b/docs/UPGRADING-3.0
index ff15ebb..0388bea 100644
--- a/docs/UPGRADING-3.0
+++ b/docs/UPGRADING-3.0
@@ -154,11 +154,18 @@ installed. You should then test with the new SLA configurations in
 a dev environment to verify that due dates are being properly set
 for all relevant actions (create, respond, resolve, etc.).
 
-Starting in 3.0.3, RTIR also disables and unapplies the SLA Custom Field since it can
-conflict with the field provided by L<RT::Extension::SLA> and cause SLAs
-not to apply properly. This change is only automated for users coming to
-3.0 or later for the first time. If you previously upgraded to 3.0.x and
-then to 3.0.3, your SLA field will not be changed.
+Starting in 3.0.3, RTIR also disables and unapplies the SLA Custom Field
+since it can conflict with the field provided by L<RT::Extension::SLA>
+and cause SLAs not to apply properly. This change is only automated for
+users coming to 3.0 or later for the first time. If you previously
+upgraded to 3.0.x and then to 3.0.3, your SLA field will not be changed.
+If you installed RTIR from the 3.0 series first, you do not have an
+extraneous SLA Custom Field.
+
+If you have two SLA Custom Fields (one from an old 2.6 RTIR install and
+one from RT::Extension::SLA) you can manually disable the incorrect SLA
+custom field and clicking on the Applies To menu in that Custom Field
+and ensuring that it is not applied to any queues, or globally.
 
 =head2 Notifications
 
@@ -214,3 +221,10 @@ Previously they were only granted rights on the default RTIR Custom Fields.
 
 Rights are managed at the Custom Field level by this script, so it's
 straightforward to remove rights after constituency creation.
+
+=head1 UPGRADING FROM 3.0.2 AND EARLIER
+
+=head2 SLA Custom Field
+
+See new additional notes in the L<SLA Support> section if you are upgrading
+within the 3.0 series.

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.