The issue converts into a replica using Outgoing sync. A replica is a copy of an issue which needs to be synchronized. You can specify information sent to the Destination instance in the Outgoing sync.
The 'replica' is handled by a processor. This transformation allows sharing the issue information over multiple issue trackers.
This page details out how each field is mapped and how this information can be accessed in the processors.
What fields can be accessed in a replica?
An array of link objects. Every link object has following fieldsotherIssueId, linkName, linkTypeName, linkType, url
id, key, name, lead, versions
Basic types are atomic types without sub fields.
|String||The java.lang.String data type is an array of characters with a maximum length of 231-1.|
|Date||Represents a specific instant in time, with millisecond precision. Should be UTC based, but might differ from server to server.|
|Boolean||True or false.|
Below you can find an example of the Outgoing sync rules with all supported issue fields sent.
Field names are case sensitive.