Scarab commit: svn commit: r10904 - branches/release/0.22/xdocs/howto/jira-import-howto.xml

Johannes Höchstädter <[email protected]>
Newsgroups gmane.comp.java.scarab.cvs
Message-ID <[email protected]>
Author: jhoech
Date: 2010-02-08 08:22:21-0800
New Revision: 10904

Modified:
   branches/release/0.22/xdocs/howto/jira-import-howto.xml

Log:
ENH - Section titles in How-To for jira import revised

Modified: branches/release/0.22/xdocs/howto/jira-import-howto.xml
Url: http://scarab.tigris.org/source/browse/scarab/branches/release/0.22/xdocs/howto/jira-import-howto.xml?view=diff&pathrev=10904&r1=10903&r2=10904
==============================================================================
--- branches/release/0.22/xdocs/howto/jira-import-howto.xml	(original)
+++ branches/release/0.22/xdocs/howto/jira-import-howto.xml	2010-02-08 08:22:21-0800
@@ -9,19 +9,20 @@
 
 <body>
 
+<section name="How to import issues from Jira">
+	<subsection name="Instructions">
+	<p>You'll need a recent version of scarab (0.22 or trunk after 2008 'april) with the JIRA templates installed. Upgrading from a previous version won't install these JIRA templates!</p>
+	<ul>
+	<li>Add attribute option values to all global option-type attributes. Then add these to the same attributes in the global issue types.</li>
+	<li>Add all users. (Alternative here is to set in build.properties scarab.import.addNewUsers=true [see the ScarabIssues.addUsers field]. This will create all the users the import process comes across on-the-fly.)</li>
+	<li>Add all the modules, adding the JIRA attributes to each. Remove the JIRA prefix from them at the same time. (If you will only have one module you can just rename the JIRA module, remembering to add the attribute options from the first step to each issue type).</li>
+	<li>Download the issues in xml format from your JIRA installation to your machine. Search and Replace all issue id prefixes so they contain only the four characters your scarab module uses. Eg SEARCH-311 must become SKER311 if your Search module has a code of SKER.</li>
+	<li>Mangle other data in the xml. For example removing customfields you won't be using any more after the import.</li>
+	<li>Go to the import xml issues under modules in the left navigation menu. Select the xml file, choose Import type: JIRA. Hit submit.</li>
+	<li>Most likely you forgot an attribute option or user and you'll see errors accordingly. Fix 'em and repeat last step.</li>
+	</ul>
 
-<section name="Instructions">
-<p>You'll need a recent version of scarab (0.22 or trunk after 2008 'april) with the JIRA templates installed. Upgrading from a previous version won't install these JIRA templates!</p>
-<ul>
-<li>Add attribute option values to all global option-type attributes. Then add these to the same attributes in the global issue types.</li>
-<li>Add all users. (Alternative here is to set in build.properties scarab.import.addNewUsers=true [see the ScarabIssues.addUsers field]. This will create all the users the import process comes across on-the-fly.)</li>
-<li>Add all the modules, adding the JIRA attributes to each. Remove the JIRA prefix from them at the same time. (If you will only have one module you can just rename the JIRA module, remembering to add the attribute options from the first step to each issue type).</li>
-<li>Download the issues in xml format from your JIRA installation to your machine. Search and Replace all issue id prefixes so they contain only the four characters your scarab module uses. Eg SEARCH-311 must become SKER311 if your Search module has a code of SKER.</li>
-<li>Mangle other data in the xml. For example removing customfields you won't be using any more after the import.</li>
-<li>Go to the import xml issues under modules in the left navigation menu. Select the xml file, choose Import type: JIRA. Hit submit.</li>
-<li>Most likely you forgot an attribute option or user and you'll see errors accordingly. Fix 'em and repeat last step.</li>
-</ul>
-
+	</subsection>
 </section>
 </body>
 </document>

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=3577&dsMessageId=2445921
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.