Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Migrating from Cloud to DC - Custom Field Error Edited

Hi all,

I'm currently migrating a Cloud instance to Jira DC and then using Project Configurator to move projects to a Dev instance. (Cloud > Temp DC > Dev)

I've backed up Cloud and restored to a temp Jira DC instance.

I'm running into an error relating to a Jira Service Management Lingo Integration plugin. On Jira Cloud, the plugin exists but it's not imported to my temp instance.

This is the plugin on Cloud:


When I use Project Configurator to export a project from the temp DC, it shows:

Found custom field with values for issues in exported project(s), with id: 11100, name: Request language and type: com.atlassian.servicedesk.servicedesk-lingo-integration-plugin:sd-request-language. This field does not exist. Check if its type is defined in a plugin that has been disabled.

I can't find the plugin to install on DC and while I can remove the field from the DB it's not going to clear the error. I also can't see the field on DC and searching for data in the field shows it doesn't exist.

I can export without contexts on custom fields but I need these to make the final migration easier.

I was hoping to just download the plugin and upload it directly to the temp DC but I can't find it.

The temp instance is running JSD 4.8.1 and Jira 8.8.1 to match the Dev instance.

Any ideas what I can do here?


1 answer

1 accepted

1 vote
Answer accepted

Managed to resolve this in the end.

On the temp instance I had, stopped Jira service and connected to the database. Deleted the trace of customfeld 11100, saved and started Jira. Can now export normally as the field is deleted.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

455 views 19 23
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you