Skip to end of banner
Go to start of banner

Mappings definitions

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 9 Current »

This page outlines the definitions found in the Field Configuration Interface and Field Mapping Interface.

Field configuration interface definitions

Reference

Field Name

Definition

1

Endpoints

Click to expand and display.

The remote system and object being connected to from Jira and the field mapping definitions for that object and Jira fields. For more information, consult Endpoints - URLs required for Salesforce configuration.

2Settings

Click to expand and display.

Allows the administrator to enable and/or disable certain mappings settings. For more information, consult Configuring the Settings for Mappings.

3

Remote System

The name of the connection used for this object mapping.

4

Remote Object Type

The name of the object being connected to.

5

Jira Outbound

Field configurations for pushing information to a remote system.

6

Jira Inbound

Field configurations for receiving information from a remote system to Jira.

Field Mapping Interface


Reference

Field Name

Definition

1

Jira Field

This is the field in Jira that you want to map the Salesforce object field to (e.g.: Subject, Description, etc.).

2

Remote Field

This is the field in the Salesforce object you want to map to. The available field values are dynamically pulled from the Salesforce object and listed for you.

3

Direction

This is to specify when the mapping will be used, this can be one of 3 options:

  • Jira to <Your Connection Name Object> Only: This means the field mapping will only be used when Jira is sending updates to the remote system (either when creating a new remote object based on a Jira issue or when updating the remote object based on the updates fields in the Jira issue).
     
  • <Your Connection Name Object> to Jira Only: This means the field mapping will only be used when Jira is receiving updates from the remote system (either when creating a new Jira issue from a remote object or when updating the Jira issue based on the updates in the remote object)
     
  • Bi-Directional: This means the field mapping will be used in all situations when a mapping is required.
  • No labels