Confluence has been updated to version 6.15.9

Expand all   Collapse all

Platforms



Skip to end of metadata
Go to start of metadata

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?

TitleFields
Attachments


id, mimetype, filename, created, filesize, author

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.

Issue


id, key, description, environment, assignee, reporter, status, resolution, type, typeName, priority, affectedVersions, fixVersions, due, resolutionDate, originalEstimate, remainingEstimate, timeSpent, project, projectKey, workLogs, labels, votes, watches, watchers, customFields, comments, components, attachments

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.

TypeComment
StringThe java.lang.String data type is an array of characters with a maximum length of 231-1.
LongThe long data type is a 64-bit two's complement integer. The signed long has a minimum value of -263 and a maximum value of 263-1.
DateRepresents a specific instant in time, with millisecond precision. Should be UTC based, but might differ from server to server.
BooleanTrue or false.


All the fields

This data filter processor will copy all the supported issue fields to a replica. 

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.resolved          = issue.resolved
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.issueLink
replica.component         = issue.component

Field names are case sensitive.