Jira to Jira service management. i’m using the visual way and it still showing error related to custom field
I just won’t sync the custom field
Comments:
Jose Pablo Alpizar Hidalgo commented on 05 May 2022
Please feel free to navigate through the several articles/links to review must relevant information for your case: https://docs.idalko.com/exalate/x/KgAT
Can you elaborate on the type of custom field you are trying to map and what is the error being received as well?
Also how are you configuring the sync? since its a scripted connection it might be useful to use a screenshot to show this.
I never add any mapping rules or script to sync the custom field to exalate , I just sync the
Comment , description , Summary, Reporter, Priority and status. only that but i still getting an error with a custom filed 10260 that i cannot find it .
services.jcloud.exception.UpdateIssueJiraCloudException: Could not update issue `INC-284` with id `30032`: Field customfield_10260: Field ‘customfield_10260’ cannot be set. It is not on the appropriate screen, or unknown… at services.node.JCloudTrackerExceptionCategoryService.generateUpdateIssueJiraCloudTrackerException(JCloudTrackerExceptionCategoryService.scala:421) at services.jcloud.transport.JCloudClient.$anonfun$updateIssue$5(JCloudClient.scala:598) at services.jcloud.transport.JCloudRestErrorHandlingService$$anonfun$recoverFromRestExceptionToJiraCloudTrackerExceptionOrBugException$1.applyOrElse(JCloudRestErrorHandlingService.scala:187) at services.jcloud.transport.JCloudRestErrorHandlingService$$anonfun$recoverFromRestExceptionToJiraCloudTrackerExceptionOrBugException$1.applyOrElse(JCloudRestErrorHandlingService.scala:180) at scala.concurrent.Future.$anonfun$recoverWith$1(Future.scala:417) at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:41) at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:64) at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:56) at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:93) at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23) at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:85) at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:93) at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:48) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:48) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183) Caused by: com.exalate.domain.exception.issuetracker.BadRequestTrackerRestException: Field customfield_10260: Field ‘customfield_10260’ cannot be set. It is not on the appropriate screen, or unknown… at services.jcloud.transport.JCloudRestErrorHandlingService$.handleTrackerFourZeroZeroAndHigherRestResponse(JCloudRestErrorHandlingService.scala:91) at services.jcloud.transport.JCloudRestErrorHandlingService$.filterTrackerRestErrorResponse(JCloudRestErrorHandlingService.scala:81) at services.jcloud.transport.JCloudClient.$anonfun$updateIssue$3(JCloudClient.scala:593) at scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:307) … 14 more
