Skip to end of banner
Go to start of banner

Field Mapping

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Current »

Fields Mapping

Local fieldSelect your local JIRA field, which you want to expose to remote JIRA instance
Local field aliasIn remote JIRA instance your (previously selected) local field will be available as what you provide here
Remote field

(alias from remote JIRA) a field (in remote JIRA instance) you will synchronize value with


How it works

Case 1: Remote field is left empty. 

  • Your local field value will not be sent to remote JIRA instance.
  • Your local field can be updated by remote JIRA instance (remote field) value.

Case 2: Remote field is selected.

  • Your field value will be propagated to remote JIRA instance (to relevant remote field).
  • Your local field can be updated by remote JIRA instance (remote field) value.


 show IssueSYNC 1.x.x...

Mapping configuration

  • Remote Contract - all configuration you do in contract concern local JIRA instance. Basically it means that data set in contract will be collected and sent to remote JIRA instance. When remote JIRA instance receive request, it doesn't know how to retrieve this data, until it match proper contract based on remote contract we sent with request. In other words, remote contract is alias that connect contract from your JIRA with the remote. 

    The list may be empty if contract was not set in remote JIRA instance. Please refer to IssueSYNC 101 in order to configure contract step by step.

  • Field Mapping - set of fields that will be synchronized. Each mapping consists of:
    • Local Field - list of local fields.
    • Local Field Name - that is the alias that will be used/visible on the remote JIRA. You can enter current field name or use own, exposed name.
    • Remote Field Name - list of all aliases/exposed fields by the remote.
  • No labels