Invalid issuetype sync from (replica) next-gen to (local) classic project

General Questions
, , ,
1

Originally asked by Cloud Chiu on 11 September 2020 (original question)

Below is the coding in incoming sync

if(firstSync){
   issue.projectKey = "XXX"
   // Set type name from source issue, if not found set a default
   issue.typeName = nodeHelper.getIssueType(replica.typeName, (issue.projectKey ?: issue.project.key))?.name ?: "Task"
}
if(issue.typeName == "Epic"){
   issue.customFields."Epic Name"?.value = replica.summary
}

I suppose for issue types syncing from replica next gen project do not exist in local classic project, the default issue type is “Task”. In the other sides, I confirm that the task issue type is set in the project’s issue type scheme.

May you tell what’s wrong with my code?

2

Answer by André Leroy-Beaulieu Castro on 19 November 2020

Francis Martens (Exalate) Cloud Chiu

This error has been resolved and documented in the following community question:

Issue Type Invalid Error - Jira Cloud (old community)

Thanks,

André