[Rt-commit] rtir branch, 2.9-trunk, updated. 2.6.1-472-geb3a285

[Ruslan Zakirov]

The branch, 2.9-trunk has been updated
       via  eb3a28508fc8510bd0f48f3d7bceaa24543b64b1 (commit)
       via  33a77563853ba7d737846bc816e17d598688fe91 (commit)
       via  5d66d3ce754854d5bda7bb16e542153d48f95b82 (commit)
      from  495072c7fee7d0f97190402223386939461b8abe (commit)

Summary of changes:
 TODO.porting_over_RT4      |   14 +++++-
 etc/RTIR_Config.pm         |   15 -------
 old-SLA-rules-and-docs.pod |  100 ++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 112 insertions(+), 17 deletions(-)
 create mode 100644 old-SLA-rules-and-docs.pod

- Log -----------------------------------------------------------------
commit 5d66d3ce754854d5bda7bb16e542153d48f95b82
Author: Ruslan Zakirov <ruz at bestpractical.com>
Date:   Wed Oct 12 02:24:42 2011 +0400

    update TODO

diff --git a/TODO.porting_over_RT4 b/TODO.porting_over_RT4
index f17c918..1b742f6 100644
--- a/TODO.porting_over_RT4
+++ b/TODO.porting_over_RT4
@@ -8,9 +8,14 @@
 * document how to switch over SLA extension, document Due
   rules for incidents
 
-=== FEATURES
+* we delete a lot of scrip actions and a few scrip conditions.
+  Warn that ALL scrips that use these will be deleted.
 
-* Split incident: select which IRs, Invs, Blocks go where
+* Delete scrips' descriptions from tutorials we have.
+
+* Review tutorials in context of lifecycles.
+
+=== FEATURES
 
 * Incident field on Create page is a mess, sometimes it's
   available for input, sometimes it's not, IRs can have
@@ -44,3 +49,8 @@ We walk the web, but there is no single functionality test for:
     .../Search/Reporting.html
     .../Reporting/index.html
     .../Split.html
+
+=== ABANDONED FEATURES
+
+* Split incident: select which IRs, Invs, Blocks go where
+

commit 33a77563853ba7d737846bc816e17d598688fe91
Author: Ruslan Zakirov <ruz at bestpractical.com>
Date:   Wed Oct 12 02:24:55 2011 +0400

    get rid of options we don't need

diff --git a/etc/RTIR_Config.pm b/etc/RTIR_Config.pm
index 04ef559..6aa4686 100644
--- a/etc/RTIR_Config.pm
+++ b/etc/RTIR_Config.pm
@@ -231,17 +231,6 @@ Set(
 
 =over 4
 
-=item C<$WebNoAuthRegex>
-
-RTIR serves URLs with F</RTIR/NoAuth/> paths that shouldn't
-be protected by authentication. If you customize this option
-make sure to include this path as well.
-
-=cut
-
-my $rt_no_auth = RT->Config->Get('WebNoAuthRegex');
-Set($WebNoAuthRegex, qr{ (?: $rt_no_auth | ^/+RTIR/+NoAuth/ ) }x);
-
 =item C<$MaxInlineBody>
 
 By default, RT only displays text attachments inline up to
@@ -470,10 +459,6 @@ Set the defaults for RTIR custom fields. Values are case-sensitive.
 
 Set(
     %RTIR_CustomFieldsDefaults,
-    SLA => {
-        InHours    => 'Full service',
-        OutOfHours => 'Full service: out of hours',
-    },
     'How Reported'  => "",
     'Reporter Type' => "",
     IP              => "",

commit eb3a28508fc8510bd0f48f3d7bceaa24543b64b1
Author: Ruslan Zakirov <ruz at bestpractical.com>
Date:   Wed Oct 12 02:25:44 2011 +0400

    add old SLA rules we had for reference

diff --git a/old-SLA-rules-and-docs.pod b/old-SLA-rules-and-docs.pod
new file mode 100644
index 0000000..07902d2
--- /dev/null
+++ b/old-SLA-rules-and-docs.pod
@@ -0,0 +1,100 @@
+=head3 Old due actions
+
+Correspond - first business minute after { queue's || config's || 7 }
+
+BySLA - some SLA calcs
+
+Reopen - SLA calc with additional settings
+
+=head2 Old starts actions
+
+Now - set to now if not setting
+ByBH - closest available business time
+
+=head2 Old rules
+
+    on create
+        Inc -> StartsNow
+        IR, Inc, Block -> StartsByBH
+    on requestor response
+        IR, Inv, Block -> DueNow
+    on staff response
+        IR, Inv, Block -> DueCorrespond
+    on move
+        IR -> DueBySLA
+        Inv, Block -> DueCorrespond
+        Inc -> StartsNow
+        IR, Inc, Block -> StartsByBH
+    on close:
+        IR, Inv, Block -> UnsetDue
+    on re-Open
+        IR, Inv, Block -> DueReopen
+
+=head2 Old config
+
+=over 4
+
+=item C<$SLAModule>
+
+Set the name of the Business::SLA class. Use this if you have
+a custom SLA module, for example:
+
+    Set($SLAModule, 'Business::MySLA');
+
+=cut
+
+Set($SLAModule, '');
+
+=item C<$SLA>
+
+Define service levels and set the number of minutes.
+
+=cut
+
+Set($SLA, {
+    'Full service'               => { BusinessMinutes => 60,    RealMinutes => 0 },
+    'Full service: out of hours' => { BusinessMinutes => 120,   RealMinutes => 0 },
+    'Reduced service'            => { BusinessMinutes => 120,   RealMinutes => 0 },
+    'Now (in business hours)'    => { BusinessMinutes => 0,     RealMinutes => 0 },
+    '60 Real Minutes'            => { BusinessMinutes => undef, RealMinutes => 60 },
+} );
+
+=item C<$BusinessHours>
+
+Set the Business Hours for your organization, for example:
+
+    Set($BusinessHours, {
+        0 => { Name => 'Sunday', Start => undef, End => undef },
+        1 => { Name => 'Monday', Start => '09:00', End => '18:00' },
+        2 => { Name => 'Tuesday', Start => '09:00', End => '18:00' },
+        ...
+    } );
+
+If left unset, defaults are Monday through Friday 09:00 to 18:00
+
+=cut
+
+Set( $BusinessHours, undef );
+
+=item C<$SLA_Response_InHours> and C<$SLA_Response_OutOfHours>
+
+Set service levels for responses in business hours and out,
+correspondingly.
+
+=cut
+
+Set($SLA_Response_InHours,    'Now (in business hours)');
+Set($SLA_Response_OutOfHours, 'Now (in business hours)');
+
+=item C<$SLA_Reopen_InHours> and C<$SLA_Reopen_OutOfHours>
+
+Set service levels for tickets re-opened in business hours and out,
+correspondingly.
+
+=cut
+
+Set($SLA_Reopen_InHours,    'Full service');
+Set($SLA_Reopen_OutOfHours, 'Full service: out of hours');
+
+=back
+

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