Dashboard > Atlassian Plugins > ... > 4. Creating JIRA issues from Salesforce.com Cases > 4.1 Salesforce.com to JIRA Mapping Configuration
  Atlassian Plugins Log In | Sign Up   View a printable version of the current page.  
  4.1 Salesforce.com to JIRA Mapping Configuration

Added by Charles Pham [CustomWare] , last edited by Jennifer Cheung [CustomWare] on Nov 24, 2008  (view change)
Labels: 
(None)

Configuration Instructions

JIRA Configuration Instructions

All custom fields containing Salesforce data need to be mapped in JIRA except for "Salesforce.com Case" and "Salesforce.com Multiple Case" custom fields, which are mapped internally. This must be done in order to indicate which fields you would like to save or sync to JIRA.

  • Login as role of Administrator

  • Click on the Administration > Salesforce.com to JIRA Mapping Configuration link. A Screen as below will be displayed.



  • Click on the 'Add New Mapping' link to add new mapping. Screen as below will be displayed.



    • Figure below shows all JIRA system fields



    • Figure below shows all JIRA custom fields



      PLEASE TAKE THE FOLLOWING PRE-CAUTIONS WHILE CONFIGURING Salesforce fields with JIRA fields.



      • For the Salesforce.com system field (other than Case Owner, Contact Name, Account Name). Please refer to the screen as below.

        • Case Reason: value for 'Salesforce.com Field Name' should be Case Reason, as screen below:



        • Case Owner: value for 'Salesforce.com Field Name' should be Owner ID, as screen below:



        • Contact Name: value for 'Salesforce.com Field Name' should be Contact ID, as screen below:



        • Account Name: value for 'Salesforce.com Field Name' should be Account ID, as screen below:



      • For the Salesforce.com custom field, refer to the example shown in the screen below:



      • Click on the 'Add' button to save the record to JIRA.
      • Please refer below for an example showing JIRA issue which populated from Salesforce.com



Copyright(c) CustomWare Asia Pacific Pty Ltd
Powered by Atlassian Confluence 2.7.3, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators