We are migrating projects from JIRA 6.1.4 to a target instance JIRA 6.4.11. The target JIRA 6.4.11 is in a production environment, it contains some other projects. So, we can only use the import project functionality instead of the restore backup system.
We have done this migration through the steps indicated by the Atlassian Support:
1. Create a new intermediate instance of the same version as the source JIRA 6.1.4.
2. Restore this intermediate instance with the backup exported from the source instance 6.1.4.
3. Upgrade the intermediate instance to the same version as the target instance 6.4.11.
4. Import the projects from the intermediate instance to the target instance.
The Intermediate instance contains the test sessions used by JIRA Capture, but the target instance does not.
How can we import the test sessions to the target JIRA?
Thank you so much for your help.
Thank you for the prompt reply.
Yes, we have upgrade the intermediate instance with the whole JIRA backup. Unlike the target JIRA instance where we have imported the projects using the import project functionality. That's why we can see the test sessions in the intermediate JIRA instance but not in the target JIRA instance. We can not perform a restore backup in the target system as we have done in the intermediate JIRA instance, because we won't loose the already existing projects.
Is there any way to import the test sessions in the target JIRA instance? Using some add-on, or doing with some sql scripts? what JJIRA database tables are used by the test sessions?
Thank you so much!
This is not an official upgrade or recommended migration path - so please proceed with a migration at your own risk.
Unfortunately there is no out-of the box migration solution available for JIRA Capture data. You would have to locate and copy the Capture related properties manually.
JIRA Capture stores it's data in JIRA Properties, they must be stored in the OS_PROPERTYENTRY.
In the OS_PROPERTYENTRY table you'll see properties with entity names:
Before proceeding on any of the environment, please prepare a database and/or JIRA backup.
Please ensure it works as you expect in the intermediate JIRA instance before applying to the production instance.
Afterwards you may need to update the related sequence values for the table (so the newly created rows would not overwrite the existing properties).
I also recommend to shut down JIRA while you manipulate the properties tables, as these might be cached on JIRA side.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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