Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Required filed error


I have Exalate enabled for 2 jira spaces (cliksupport and asiasupport247). I was not able to sync the issue from space A to B due to below error. I've checked the filed and required setting for both sites, they are the same, however error still persist. Can I know where I can look into further to resolve this error ? 

Error Detail Message:
Field AM in Charge is required.: customfield_10090; Field System Type is required.: customfield_10091; Field Market is required.: customfield_10092; Field Enable Progressive Games is required.: customfield_10093; Field Enable Live Dealer is required.: customfield_10094; Field Operator Name is required.: customfield_10084; Field Estimated Go Live Date is required.: customfield_10095; Field Brand Name is required.: customfield_10085; Field New Operator ? is required.: customfield_10087; Field Environment requested is required.: customfield_10089.

Thank you



3 answers

3 accepted

Hey @Jane Kao ,
Jose from Exalate's Sales team here.

Were you able to create the support ticket?

You can do it by emailing this information to


Let me know if you need any further assistance,

0 votes
Answer accepted

As @Nic Brough -Adaptavist- mentioned, I'd also look if all the required fields are filled in the source issue - and additionally if you've included them in your mapping within Exalate.

If that doesn't bring you further, you can contact the Exalate support.

0 votes
Answer accepted

Are all the fields filled (with matching options if the fields are not plain text) in the source issue?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events