Confluence has been updated to version 6.15.9

JIRA SERVER JIRA CLOUD ZENDESK

There might be multiple use cases in issue types synchronization.

With Exalate, you can handle any possible combination of the issue type mapping.

Source side

To send the issue type, add this script  below to the Outgoing sync

replica.type = issue.type

Destination side

There are different approaches to how you can set the issue type on the receiving side, depending on your specific use case. 

To add the issue type on a synced issue you should add the script to the Incoming sync. 

Below you can find some of the most common cases:

  • Set the issue type name from the source issue, if not found set a default one

    // Set type name from source issue, if not found set 'Task' as the default target issue type
    issue.typeName     = nodeHelper.getIssueType(replica.type?.name, issue.projectKey)?.name ?: "Task"

  • Set the issue type according to the mapping, specified with the help of Groovy scripts

    //map issue types between source and destination instances.
    def issueTypeMapping = [
    // "remote issue type" : "local issue type"
      "Bug" : "Problem",
      "Task" : "Assignment"
    ]
    
    issue.typeName = issueTypeMapping[replica.type?.name] ?: "Assignment"

See also

How to sync multiple projects with multiple issues types?

What is the difference between issue.type and issue.type.name?