[Rt-commit] rtir branch, 2.9/modernize-doc, updated. 2.6.1-520-ge3ff657

[Ruslan Zakirov]

The branch, 2.9/modernize-doc has been updated
       via  e3ff65732345276e8d5ad5d1d9f203ed66ccf664 (commit)
       via  628b186430d1d590490e00b77eb28567c4170b4b (commit)
      from  79569ebf1c9ed5fb36d29eb7098ab0a22e7ccafb (commit)

Summary of changes:
 README                 |   12 ++++++++----
 lib/RT/IR/Tutorial.pod |   34 +++++++++++-----------------------
 2 files changed, 19 insertions(+), 27 deletions(-)

- Log -----------------------------------------------------------------
commit 628b186430d1d590490e00b77eb28567c4170b4b
Author: Ruslan Zakirov <ruz at bestpractical.com>
Date:   Fri Oct 21 13:31:01 2011 +0400

    mention RTx::SLA in README

diff --git a/README b/README
index 690d83b..ff744bb 100644
--- a/README
+++ b/README
@@ -51,11 +51,15 @@ Installation instructions:
 
 8) Stop and start your web server.
 
-9) If you want to enable ticket/incident aging, install RT::Extension::TicketAging
-   following the installation instructions in that extension's INSTALL and README 
-   files.
+9) To maintain Due date of Reports, Investigations and Blocks install
+   RT::Extension::SLA following the installation instructions in that
+   extension's README files.
 
-10) If you want to enable ticket locking, install RT::Extension::TicketLocking
+10) If you want to enable ticket/incident aging, install RT::Extension::TicketAging
+    following the installation instructions in that extension's INSTALL and README
+    files.
+
+11) If you want to enable ticket locking, install RT::Extension::TicketLocking
     following the installation instructions in that extension's README file.
 
 

commit e3ff65732345276e8d5ad5d1d9f203ed66ccf664
Author: Ruslan Zakirov <ruz at bestpractical.com>
Date:   Fri Oct 21 13:36:06 2011 +0400

    bring tutorial up to date

diff --git a/lib/RT/IR/Tutorial.pod b/lib/RT/IR/Tutorial.pod
index 50fcfe1..bb0a86f 100644
--- a/lib/RT/IR/Tutorial.pod
+++ b/lib/RT/IR/Tutorial.pod
@@ -107,7 +107,7 @@ are joined with respective properties of ticket #2: TimeEstimated,
 TimeWorked, TimeLeft, Requestors, Cc and AdminCc and links.
 Duplicated links or watchers will be condensed, also if there
 were links between tickets #1 and #2 then RT will drop them.
-Other fields from ticket #1 are ignored, such as state, queue or
+Other fields from ticket #1 are ignored, such as status, queue or
 custom fields of single value type. By default RTIR shows only
 active tickets as candidates for the merge, so you have no way
 to merge a ticket into one that's been resolved or rejected,
@@ -154,7 +154,7 @@ When you open a ticket's display page there is a 'Reject' tab. You click
 it and see 'reject Incident Report' page with a box for message and other
 common input fields. You can write a message and choose whether it would be
 comment or response, by default correspondents don't receive comments.
-You submit the form and RTIR sets state of the ticket, records the message
+You submit the form and RTIR sets status of the ticket, records the message
 and unlink the IR from any Incidents.
 
 If you don't want to write any comment or change any properties of an IR
@@ -164,8 +164,8 @@ the reject form.
 
 =head4 Rejecting many IRs at once (bulk reject)
 
-On the RTIR home page at the bottom of 'New unlinked Incident Reports' box
-you can see 'Bulk Reject' link. Following that link you can open interface
+On the RTIR home page at the top right corner of 'New unlinked Incident Reports'
+box you can see 'Reject' link. Following that link you can open interface
 for rejecting many tickets at once. The interface has a buttons to
 check/uncheck all tickets on the page or you can select particular IRs
 with checkboxes. To reject tickets you submit the form with 'reject' or
@@ -173,9 +173,9 @@ with checkboxes. To reject tickets you submit the form with 'reject' or
 'bulk reject' page, while the latter one returns you to the RTIR home page
 where you could continue your work.
 
-As well, link to 'Bulk Reject' operation exist at the bottom of searches for
-'Incident Reports', so you can go to RTIR's 'Incident Reports' menu, refine
-search conditions if you like to, and from the page with results go to
+As well, link to 'Bulk Reject' operation exist in the page menu of searches
+for 'Incident Reports', so you can go to RTIR's 'Incident Reports' menu,
+refine search conditions if you like to, and from the page with results go to
 'Bulk Reject' operation.
 
 Using this interface you can reject IRs that have links to Incident(s) what
@@ -292,13 +292,13 @@ and linking them to this IR by clicking the "[New]" button next to the
 
 =head4 Linking Incidents to IRs, Investigations, etc.
 
-You may link Incidents with existing Incident Responses, Investigations,
+You may link Incidents with existing Incident Reports, Investigations,
 Blocks, and Articles. On the Incident display page there are sections for
 each of these, each with a C<Link> button and the list of already-linked
 tickets. Clicking on C<Link> lets you link one or more tickets of that type to
 the Incident.
 
-Clicking on C<New> (or in the case of Investigations, C<Launch>) lets you
+Clicking on C<Create> (or in the case of Investigations, C<Launch>) lets you
 create a new tickets and link it to the Incident automatically.
 
 =head3 Resolution
@@ -331,8 +331,7 @@ fill in a message or time worked, attach files, and so on.
 =head4 Launching an Investigation
 
 To launch a new Investigatin, create a new ticket in the Investigation queue.
-You will be required to link the Investigation to an Incident, and provide one
-or more correspondents.
+You will be required to provide one or more correspondents.
 
 =head3 Blocks
 
@@ -356,21 +355,10 @@ if you need wider one-column layout.
 
 =item QuickSearch
 
-Lists RT's queues with summary on numbers of active tickets in those.
+Lists queues with summary on numbers of active tickets in those.
 Allows you to quickly jump to all active tickets in a queue or to tickets
 with particular status.
 
-Note that RTIR's queues are hidden from the list as QuickSearch box
-is not flexible enough to build desired report by RTIR's states.
-New/open/stalled statuses just don't make much sense in RTIR, so we
-hide RTIR's queues. Use /RTIR/Elements/QueueSummary portlet instead.
-
-=item /RTIR/Elements/QueueSummary
-
-Lists RTIR's queues with summary on numbers of active tickets in those.
-Allows you to quickly jump to all active tickets in a queue or to tickets
-with particular state.
-
 =item Other
 
 There are more portlets you use which names are quite self-descriptive.

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