Apps documentation
Issue SYNC for Jira Cloud
Issue SYNC for Jira Cloud
Introduction
Architecture & Versions
Development
Last updated Nov 1, 2020

How to synchronize fields

Assumption: you already have created the connection and contract.

Field mapping is used to point to remote fields. You can choose which fields you want to synchronize with remote Jira.

Local field is a name of a field from issue, which you want to expose, those will be sent to the remote Jira. Remote Field name is an alias, which will be presented in remote Jira instance.

Remote Jira administrator will be able to consume them and map them to fields in remote (their) issue.

To edit them just click on “Edit” button, then a dialog will appear. Here you can add or remove fields you want to send to the remote Jira instance. When you finish selecting the fields, just click “Save” button.

“Fields to send” component will refresh and present you the fields you are exposing to remote Jira instance.

Supported field types

System fields

FieldType ServerToCloud CloudToServer CloudToCloud
description (Yes) (Yes) (Yes)
summary (Yes) (Yes) (Yes)
priority (Yes) (Yes) (Yes)
labels (Yes) (Yes) (Yes)
resolution (read only) (Yes) (Yes) (Yes)
assignee (Yes) (Yes) (Yes)
reporter (Yes) (Yes)only to text fields (Yes)
affects version/s (Yes) (Yes) (Yes)
fixversions (Yes) (Yes) (Yes)
components (Yes) (Yes) (Yes)
duedate (Yes) (Yes) (Yes)
creator (read only) not supported by server (Yes) (Yes)
status (read only) not supported by server (Yes) (Yes)
created (read only) (Yes) (Yes) (Yes)
updated (read only) (Yes) (Yes) (Yes)

Custom fields

FieldType ServerToCloud CloudToServer CloudToCloud
user picker (Yes) (Yes) (Yes)
user picker multiple (No) (Yes) ?
single select (Yes) (Yes) (Yes)
multi select (Yes) (Yes)but only from multi select (Yes)
textfield (Yes) (Yes) (Yes)
unlimited textfield (Yes) (Yes) (Yes)
number (Yes) (Yes) (Yes)
date (Yes) (Yes) (Yes)
datetime (Yes) (Yes) (Yes)
cascade select not supported by server (Yes) (Yes)