[Rt-commit] r9113 - in rtir/branches/2.3-EXPERIMENTAL: .

sartak at bestpractical.com sartak at bestpractical.com
Fri Sep 21 14:31:52 EDT 2007


Author: sartak
Date: Fri Sep 21 14:31:51 2007
New Revision: 9113

Modified:
   rtir/branches/2.3-EXPERIMENTAL/   (props changed)
   rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/AdministrationTutorial.pod
   rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/DocIndex.pod
   rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/Tutorial.pod

Log:
 r42986 at onn:  sartak | 2007-09-21 14:31:43 -0400
 Spec wants some doc on what is recoverable


Modified: rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/AdministrationTutorial.pod
==============================================================================
--- rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/AdministrationTutorial.pod	(original)
+++ rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/AdministrationTutorial.pod	Fri Sep 21 14:31:51 2007
@@ -32,10 +32,14 @@
 
 See the documentation for L<RT::Extension::TicketAging>
 
-=head2 Maintaining DB size, deleting entries
+=head2 Maintaining DB size, deleting entries, restoring deleted data
 
 During normal operation RT/RTIR never deletes data from the database.
 Since RT 3.7 the RTx::Shredder extension has been integrated into
 RT.  This extension can remove data such as Users or Tickets
 from the RT/RTIR system. You can find documentation for this 
 extension in in L<RT::Shredder>  by running `perldoc lib/RT/Shredder.pm`
+RT::Shredder's documentation includes information on restoring deleted data
+from backups. RT::Shredder provides SQL commands to reverse any delete
+operations, so any data that it deletes may be restored.
+

Modified: rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/DocIndex.pod
==============================================================================
--- rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/DocIndex.pod	(original)
+++ rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/DocIndex.pod	Fri Sep 21 14:31:51 2007
@@ -32,10 +32,6 @@
 
 =back
 
-=head3 Create new Incident from IR via 'Basics' section
-
-TODO: does this need further explanation or can it be lumped?
-
 =head3 Create new block via web-interface
 
 L<Tutorial/'Creating a Block'>
@@ -58,12 +54,17 @@
 
 L<Tutorial/'Rejecting many IRs at once (bulk reject)'>
 
+=head3 Linking IRs to Incidents
 
-=head3 Link IR with new Incident
+=over 4
 
-L<Tutorial/'Linking IRs to Incidents'>
+=item Link IR with new Incident
 
-=head3 Link IR with existing Incident
+=item Create new Incident from IR via 'Basics' section
+
+=item Link IR with existing Incident
+
+=back
 
 L<Tutorial/'Linking IRs to Incidents'>
 

Modified: rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/Tutorial.pod
==============================================================================
--- rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/Tutorial.pod	(original)
+++ rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/Tutorial.pod	Fri Sep 21 14:31:51 2007
@@ -263,7 +263,7 @@
 If you have an existing IR, you can link it to an Incident by clicking the
 "[Link]" button next to the "Incident" field. You may also create new Incidents
 and linking them to this IR by clicking the "[New]" button next to the
-"Incident" field.
+"Incident" field in the "The Basics" section of the IR display.
 
 =head4 Linking Incidents to IRs, Investigations, etc.
 
@@ -289,8 +289,7 @@
 =head4 Creating a Block
 
 To create a new Block, create a new ticket in the Blocks queue. You will be
-required to link the Block to an Incident. (needs more info from someone
-knowledgeable)
+required to link the Block to an Incident.
 
 =head2 Custom fields
 


More information about the Rt-commit mailing list