[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rt-commit
Subject:    [Rt-commit] r6119 - in rtir/branches/2.1-EXPERIMENTAL: .
From:       ruz () bestpractical ! com
Date:       2006-09-29 10:30:40
Message-ID: 20060929103040.B8F2C4D80AE () diesel ! bestpractical ! com
[Download RAW message or body]

Author: ruz
Date: Fri Sep 29 06:29:42 2006
New Revision: 6119

Modified:
   rtir/branches/2.1-EXPERIMENTAL/   (props changed)
   rtir/branches/2.1-EXPERIMENTAL/docs/Tutorial.pod

Log:
 r1657@cubic-pc:  cubic | 2006-09-29 14:39:03 +0400
 * merge op clarification in docs


Modified: rtir/branches/2.1-EXPERIMENTAL/docs/Tutorial.pod
==============================================================================
--- rtir/branches/2.1-EXPERIMENTAL/docs/Tutorial.pod	(original)
+++ rtir/branches/2.1-EXPERIMENTAL/docs/Tutorial.pod	Fri Sep 29 06:29:42 2006
@@ -38,7 +38,9 @@
 The second box contains other tickets you can merge into, 
 tickets are grouped by type, if it's possible to merge the
 ticket into a ticket of another type. (for example, you can
-merge an IR into an Investigation).
+merge an IR into an Investigation). Note that if a user
+merges an IR into an Investigation then investigation is always
+used as the target ticket.
 
 You have to select one ticket from the list and submit form the.
 If the merge completes succesfully, you'll be redirected to the 
_______________________________________________
Rt-commit mailing list
Rt-commit@lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-commit
[prev in list] [next in list] [prev in thread] [next in thread]