Error Syncing from Jira server to Azure

General Questions
, ,
1

Originally asked by Gary Crabtree on 02 September 2020 (original question)

I am having an error syncing from Jira server to Azure. I keep getting the following error:

Script error for issue 163. Details: No such property: issue for class: Script1. Error line: Script1.groovy:1

It is super generic, and I don’t know where to look to correct it. Any help would be appreciated. Source: Azure DevOps (old community)

Comments:

Gary Crabtree commented on 02 September 2020

I see this error on the Jira side

2

Answer by Juan Grases on 04 November 2020

Hi!

This error means that the issue variable is not accessible when syncing, I would assume this is happening because this is the sync related to a sprint. If so, please follow the scripts from here:

https://docs.idalko.com/exalate/x/rgF1Aw

Basically you need to wrap your issue related code on :

if(entityType == "issue"){
  //Your code
}
3

Answer by Francis Martens (Exalate) on 02 September 2020

Exalate is using groovy scripts to convert work items into messages and messages into issues (and the way back)

You will be able to find these scripts embedded in the connection that you created.

First question - do you see this error on the ADO side or on the Jira side?

Comments:

Gary Crabtree commented on 09 September 2020

The error is from the Jira side.