Issue fields available for synchronization

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?

Title	Fields
Attachments	id, mimetype, filename, created, filesize, author
ChangeHistory	id, author, created, changeItems
ChangeItem	Field, FieldType, From, FromValue, To, ToValue
Comment	id, author, body, created, updated, updateAuthor, groupLevel, roleLevel, executor
Component	id, description, lead, leadKey, name, projectId, projectKey, assigneeType
CustomFields	id, name, type, value
Entity Properties	The entityProperties is an array of objects which can be used to carry any type of information and then it will be saved as entity properties for an issue.
Issuetype	id, name, description
Label	label
Links	otherIssueId, linkName, linkTypeName, linkType, url
Option	id, sequence, disabled, parentOption, childOptions, value
Priority	id, name, description
Project	id, key, name, lead, versions
Resolution	id, name, description
SecurityLevel	id, name
Status	id, name, description
User	id, key, username, active, email, displayName
Version	id, name, description, projectkey, archived, released, releaseDate, startDate
Watchers	The list of users watching the issue
Worklog	id, author, body, created, updated, updateAuthor, startDate, timeSpent, comment

Basic types

Basic types are atomic types without sub fields.

Type	Comment
String	The java.lang.String data type is an array of characters with a maximum length of 2³¹-1.
Long	The `long` data type is a 64-bit two's complement integer. The signed long has a minimum value of -2⁶³ and a maximum value of 2⁶³-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.

replica.key               = issue.key
replica.summary           = issue.summary
replica.description       = issue.description
replica.environment	      = issue.environment
replica.assignee          = issue.assignee 
replica.reporter          = issue.reporter
replica.creator           = issue.creator
replica.status            = issue.status
replica.resolution        = issue.resolution
replica.type		      = issue.type
replica.priority          = issue.priority
replica.created           = issue.created
replica.updated           = issue.updated
replica.resolutionDate    = issue.resolutionDate
replica.affectedVersions  = issue.affectedVersions
replica.fixVersions       = issue.fixVersions
replica.due               = issue.due
replica.originalEstimate  = issue.originalEstimate
replica.remainingEstimate = issue.remainingEstimate
replica.timeSpent         = issue.timeSpent
replica.project           = issue.project
replica.workLogs          = issue.workLogs
replica.labels            = issue.labels
replica.comments          = issue.comments
replica.votes             = issue.votes
replica.watches           = issue.watches
replica.watchers          = issue.watchers
replica.customFields      = issue.customFields
replica.attachments		  = issue.attachments
replica.issueLinks        = issue.issueLinks
replica.components        = issue.components

Content

Space Tools

What fields can be accessed in a replica?

Basic types