Questions for Confluence license has expired.

Please purchase a new license to continue using Questions for Confluence.

GitHub error when issue is closed

 
1
0
-1

I have a Jira cloud and GitHub sync setup with Exalate. However, when the issue gets closed (from GitHub), I get the following error:

Updated Issue: {"title":"","labels":[],"state":"closed","milestone":null} - 422 Validation Failed. 
    at services.node.client.ClientHelper.filterResponse(ClientHelper.scala:45)
    at services.node.client.GithubClient.$anonfun$updateIssue$4(GithubClient.scala:622)
    at scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:307)
    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)
    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Whenever an issue is closed in GitHub, it will not be possible to do any updates to it. This is GitHub specific behaviour. In order to update the issue, you must re open it.

        CommentAdd your comment...