Creating a New Mapping

The mandatory mappings are configured by default. You can view default mappings, add custom field mappings, and override default field mappings.

Notes:
  • To use the Certinia Help Mappings Lightning page and Foundations Mapping component, you must have the Certinia Help - Configure Jira and FDN Core - Mapping permission sets assigned. Contact your administrator if you require these permission sets. For more information, see Permission Sets and Other Technical Documentation. Before you start mapping a field to a Jira Issue field, assign permissions to the objects and fields. Even if you do not assign object and field permissions for the Project and Project Task, you can still view the existing mappings while adding or editing the mappings, but you cannot select any object or field.
  • You can only perform these steps in Lightning if the latest packages of Foundations, PSA, and Certinia Help extension packages are installed.

To create custom field mappings using the Lightning Page, perform the following:

  1. Open the Certinia Help Mappings Lightning page.
  2. In the relevant field mapping components, you can:
    • View the source and target objects.
    • View the source and target fields for each mapping.
    • Add custom mappings.
  3. Override the default (managed) mappings.
  4. Save custom mappings.

For more information, see Adding Custom Mappings from the FDN Mappings Component.

Using Advanced Lookups to Populate Relationships Based on Jira Field Values

If you want to populate lookups on the target object, you can use the standard field mapping. This requires the Salesforce ID of the target-related object to be in the source object.

However, using the Advanced Lookup field, you can also use an alternative way to populate lookups on the target object. It allows the related object to be found by one, or two, and only one or two arbitrary fields on the related object using values from the input object. This is done only if you do not want to synchronize or correlate projects between PSA and Jira but rather have a field on the issue in Jira identifying the PSA project. As Project Tasks require a project, the managed mapping to find a PSA Project based on the key of the Jira project has to be replaced.

You can reuse the Linked PSA Project custom metadata setup from Example 2 - For Non-Scalar Custom Field. In this example, a custom field on the PSA project is labeled Jira Project Identifier. For this to work, ensure the value in the Jira Project Identifier field in PSA exactly matches the value on the picklist in Jira.