How to limit data directory for single project export?

Steinar Bang

I need to move a single project from a hosted JIRA to cloud JIRA.

The recommended procedure is to:

• Export the entire hosted JIRA as XML
• Export the hosted JIRA data directory (where the attachments live)
• Spin up a test instance of JIRA that is the same version as the hosted JIRA
• Do a single project import into the test instance
• Upgrade the test instance to the newest version of JIRA
• Do an XML export of the test instance
• Import the test instance's XML export in Clould JIRA
• Upload the data directory to cloud JIRA

What the procedure doesn't cover, is how to limit the data directory to just the attachment that belong to the single exported project?

Should the data directory be imported into the test instance?  When should it be imported to the test instance? (before the upgrade? After the upgrade?)  Will a garbage collection be run automatically on the attachments? Do a garbage collection need to be run manually on the attachments?

Or isn't it necessary to do any limitation of the data directory, because cloud JIRA will drop all uploaded orphaned attachments on the floor?

 

Thanks!

Steinar

 

Nic Brough -Adaptavist-

You have to do the "limit data to current project" by hand, because JIRA has no way of knowing what you are actually planning to do.  Unless you explicitly delete all the projects you don't want to transfer when you're working in the temporary test system, it can't know what you're doing.  The attachments directory has a clear structure though - it's easy to see what directory contains the project - just delete all the others after you've restored it from Cloud