<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Valtech Blogs &#187; installation support</title>
	<atom:link href="http://blogs.valtech.com/blog/tag/installation-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.valtech.com</link>
	<description></description>
	<lastBuildDate>Mon, 26 Jul 2010 11:17:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to migrate a Jira project from Jira Enterprise (with crowd) to Jira Professional</title>
		<link>http://blogs.valtech.com/jom/2009/06/07/how-to-move-a-jira-project-from-jira-enterprise-with-crowd-to-jira-professional/</link>
		<comments>http://blogs.valtech.com/jom/2009/06/07/how-to-move-a-jira-project-from-jira-enterprise-with-crowd-to-jira-professional/#comments</comments>
		<pubDate>Sat, 06 Jun 2009 22:26:57 +0000</pubDate>
		<dc:creator>Josef Markgraf</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[atlassian]]></category>
		<category><![CDATA[EN]]></category>
		<category><![CDATA[hint]]></category>
		<category><![CDATA[installation support]]></category>
		<category><![CDATA[JIRA]]></category>

		<guid isPermaLink="false">5.3</guid>
		<description><![CDATA[We are running Atlassian JIRA Enterprise 3.13.2 with Atlassian Crowd as SSO system and use it for our client projects. Once and a while we have to move the JIRA project from our jira enterprise installation to a jira instance at the client side for later reference. This is exactly what I had to do a couple of days ago.]]></description>
			<content:encoded><![CDATA[<p>We are running<strong> </strong>Atlassian JIRA Enterprise 3.13.2 with Atlassian Crowd as SSO system and use it for our client projects. Once and a while we have to move the JIRA project from our jira enterprise installation to a jira instance at the client side for later reference. This is exactly what I had to do a couple of days ago.</p>
<p>Unfortunately the client uses a JIRA professional with the JIRA internal user management and JIRA currently doesn&#8217;t support import of the project between two different versions (Ent &#8211; Pro).  I assume, there are more people out there having the same &#8220;problem&#8221;. It was a manual process but did work in the end.</p>
<h3>Prepare the local JIRA installations:</h3>
<ul>
<li>Install a local JIRA Enterprise &#8211; <strong><em>not using the inmemory database</em></strong></li>
<li>First create a <strong>backup</strong> from your JIRA installation and <strong>restore</strong> it on a local JIRA enterprise installation. Unfortunately <strong>you can not connect</strong> to the local jira enterprise as you most likely don&#8217;t the users and passwords.<br />
<em>Note the users stored in crowd will not be part of the backup/restore. </em></li>
<li>If you can connect to the local JIRA enterprise <strong>skip the next steps</strong>.</li>
<li>Next install a local JIRA Professional and create an admin user. Connect to the local database and export the data of the <strong><em>table</em></strong> <strong>userbase</strong>. You need to know the <strong>password</strong> as it is stored in the database, in the <strong><em>encrypted</em></strong> format.</li>
<li>Connect to the database of the local JIRA Enterprise and check if there are any users in the <strong><em>table</em></strong> <strong>userbase</strong>. <em><br />
</em></li>
<li>Update the password of the admin user in the database or if the user is missing &#8211; create the user in the database <strong><em>table</em></strong> <strong>userbase </strong>using plain SQL.</li>
<li>Now you should be able to <strong>connect</strong> to the local JIRA Enterprise installation</li>
</ul>
<h3>Cleanup the local JIRA Enterprise</h3>
<ul>
<li>Switch off <strong>external user management</strong></li>
<li><strong>Delete</strong> all other <strong>projects</strong></li>
<li><strong>Delete</strong> <strong>users</strong> and <strong>groups</strong> which are not needed any more</li>
<li><strong>Delete</strong> any <strong>customizations</strong> or set it as <strong>default</strong>. Customizations are i.e.
<ul>
<li><strong>workflows</strong></li>
<li><strong>permission</strong> <strong>schemes</strong></li>
<li><strong>issue types, screens and screen schemes</strong></li>
<li>&#8230;</li>
</ul>
</li>
<li>Change the project <strong>configuration</strong> (of the only project left over)
<ul>
<li><strong>Issue Security Scheme</strong> is set to <strong>None</strong>.</li>
<li><strong>Field Configuration Scheme</strong> is set to <strong>System Default Field Configuration</strong>.</li>
<li><strong>Issue Type Screen Scheme</strong> is set to <strong>Default Issue Type Screen Scheme</strong>.</li>
<li><strong>Workflow Scheme</strong> is set to <strong>None</strong>.</li>
<li><strong>Project Category</strong> is set to <strong>None</strong>.</li>
</ul>
</li>
<li>Create a <strong>backup</strong> of the JIRA Enterprise Installation</li>
<li><strong>Restore the backup </strong>into the local JIRA Professional</li>
<li>Now <strong>configure</strong> the local JIRA Professional according to your needs</li>
</ul>
<p><em><strong>And you&#8217;re done with it.</strong></em><br />
Create a new Backup or project export and Import it into the JIRA Professional Version.</p>
<p>This process did work for us and I hope it will help you resolving this issue if it will arise.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.valtech.com/jom/2009/06/07/how-to-move-a-jira-project-from-jira-enterprise-with-crowd-to-jira-professional/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
