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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Jira Cloud Migration Error Edited

We want to move 3 projects from our OnPremise Jira server to Jira Cloud. In this process I am executing a trial migration on these projects using Jira Cloud Migration assistant tool. We are getting below errors when migration tool tries to import project data. It is migrating users successfully.

2021-04-27 15:13:34.991 ERROR ABC project-export We couldn't export Custom Field Config Scheme 'Global'. Reason: java.lang.NullPointerException.
2021-04-27 15:14:43.141 ERROR ABC project-export We couldn't export Custom Field Config Scheme 'Global'. Reason: java.lang.NullPointerException.

 

Note: I cant see any 'Global' field configuration schema in Jira application (in browser) i.e. my on-premise server acting as source. Any pointers around it on where to check further on this?

Environment in use:

OnPremise Jira server v8.2.0#802000

JIRA Cloud having trial plan

Apps in use: Tempo Timesheet, JSU Automation

2 answers

1 accepted

0 votes
Answer accepted

Hi @Jayant

I am wondering if it could help to copy the current Field Configuration Scheme to a similar named for a test, assign it correctly to the currently failing projects, then re-run the export.

This is just a guess, though - in case this will not fix the issue probably the best would be to raise a request with Atlassian's cloud migration support.

Regards,
Daniel

Hi @Daniel Ebers , I have raised this to Atlassian Support. Looks like its bug in JCMA and Atlassian team is working on it.

The new field configuration will have new id generated however existing conflicting situation remains same in database

1 vote

Hi! 

Please, take a look the Custom Field Config Scheme 'Global'.

Then checkout the custom field scheme. 

Hi @Gonchik Tsymzhitov , there is no any Custom field config scheme as 'Global'. Can you please point out how do I access it?

How many Custom field config schemes do you have ?

Do you have project  ABC ? If so, please, check connected field config schemes

I have 13 configuration schemes and none of them is named as Global. I checked the associated field configuration scheme for my project and didnt find anything wrong or field name Global

I checked in database and found that there exists 4 rows in fieldconfigscheme table, but not able to corelate why its not getting displayed on UI. Any clues how to find missing link here will be helpful.

Suggest an answer

Log in or Sign up to answer
TAGS

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