Presently we have JIRA 4.2.4 version which is installed on a Windows 2003 box, as per validation strategy I have installed JIRA 5 on my DEV box to test and if things look good i will install JIRA 5 on a new 2008 box make it production - retire 4.2.4 box. Now I want to see production similar data in my JIRA 5 box, I have read some of the documents available and listed the steps which I have to take to see Production similar data in my DEV box.
Kindly review the same and let me know if my approach is correct or needs any corrections,
1) Login to Administration Tab of JIRA 4.2.4 Production server and click on “Backup Data to XML” and backup as PROD_BACKUP.zip of the available data.
2) Login to JIRA 4.2.4 Production server and take the backup of attachments folder “<Jira Install Directory>\data\attachments”
3) Login to JIRA 5 server and place the PROD_BACKUP.zip file to “D:\Program Files\Atlassian\Application Data\JIRA\import” and attachments to “D:\Program Files\Atlassian\Application Data\JIRA\import\attachments”
4) Login to Administration Tab of JIRA 5 Dev instance and click on ‘Project Import’ under System tab and import the projects.
There's one extra thing that you might be able to do.
If you have started to create custom fields, custom workflows, etc, on your JIRA 5 DEV system then you will lose all that work when you perform the XML import from your Production server. The import will be data AND configuration, overwriting what already exists.
Well, some of this can be preserved. You can use the new Workflow Sharing Plugin to export your development workflows from DEV before you perform your XML import. The workflow export will include custom fields, statuses, workflow layout, and even the plugins required for the workflow.
After importing your XML to DEV it should be very easy to re-install the Workflow Sharing Plugin and then import the workflows that you have previously exported... thus recreating all those custom fields, etc.
Now, this won't take care of stuff like custom event configuration, etc. But it can still save hours (days) of work.
The complete XML import wlll take care of all your projects. After the import, your DEV server will have all the projects and all the issues from your Production server... and all the configuration too. Thus, after import you might want to do something to stop notifications & subscriptions.
One extra thing about XML import... if you are connecting an external system to JIRA using SOAP (example, the Mylyn Plugin for Eclipse) then check your system logs. If you get an Exception "PasswordEncoderNotFoundException" then it will necessary to restart JIRA. See: JRA-25757.
Project import only imports the issue data for a project - it won't work if you want everything, and if you really do only want a couple of projects, you'll need to set up their fields, workflows, and so-on before importing the issues.
The full import imports everything, all the config, all the project data, all the users, all the issues, ... , everything except attachments (which you've already covered correctly)
I tried performing the above 4 steps but Step 4 failed because "JIRA 4.2.4 Project will not get imported to JIRA 5.1" , we should be having same versions to import it seems.
So the migration steps is the only way i think to have production similar data. I will read the migration documents and write steps now ..
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs