Import Projects from 6.4 to 7.3.2

Hi,

On our current production installation, we're currently running Jira v6.4.12 with Jira Agile v6.7.16 and Jira Service Desk v2.5.9

We're hoping to stand up a completely new instance of v7+ and only import the relevant few projects and discard the rest.  We're seeing this opportunity as a 'clean slate' approach.

Our progress thus far is as follows:

- Created Snapshot of back end and application server

- Upgraded current prod instance straight to v7.3.2 as well as installing Service Desk v3.3.2

- Exported current projects

- Reverted to snapshot to resume working

So we've now got the current xml's that have been generated and have completetly created a new v7.3.2 instance and am trying to import the select few projects that we want and am running into dramas...

Upon the importation, we're receiving 3 errors to the effect of:

The backup project 'Development Business As Usual ' requires custom field named 'Customer Request Type' with full key 'com.atlassian.servicedesk:vp-origin'. In the current instance of JIRA the plugin is at version '3.3.2-REL-0010', but in the backup it is at version '2.5.9'.

The backup project 'Development Business As Usual ' requires custom field named 'Request participants' with full key 'com.atlassian.servicedesk:sd-request-participants'. In the current instance of JIRA the plugin is at version '3.3.2-REL-0010', but in the backup it is at version '2.5.9'.

The backup project 'Development Business As Usual ' requires custom field named 'Time to resolution' with full key 'com.atlassian.servicedesk:sd-sla-field'. In the current instance of JIRA the plugin is at version '3.3.2-REL-0010', but in the backup it is at version '2.5.9'.

These are in fact default fields that are not 'custom' ones that we've added, but part of the original SD plugin.  These are completely locked, which leaves only the version discrepancy being the issue.

Now the problem is that there is no way to upgrade the older plugin individually (although we did install the new SD software over the top as part of the test upgrade path).  The older SD plugin in use is an EOL product and has been integrated and implemented into the core Jira product as of V7 onwards.

How are we able to work around this issue?

I've found a few articles on upgrading from v6.x to v7 and it would appear that its most recommended that we go to the base 7.0.0 version first?  Is this where the issues lies, that we've tried to jump to far up?

https://community.atlassian.com/t5/JIRA-questions/Migrating-Jira-6-3-to-7-0-Jira-Software-best-way/qaq-p/580103

https://confluence.atlassian.com/jirakb/project-import-error-due-to-required-plugin-custom-field-282169482.html

Any assistance would be greatly appreciated!

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

67 views 0 1
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you