Editing Existing Mappings

You can edit a custom mapping on the PSA field to a Jira Issue field containing a unique target field, child relationship mappings, a unique target field, and target child type. If a managed mapping exists with the same information, the custom mapping overrides it.

Note:

When you make changes on a Certinia Help Mappings Lightning page, then the changes get displayed in the Custom Metadata Types and vice-versa.

Editing Custom Field Mappings using the Lightning Page

To edit mappings:

  1. Open the Certinia Help Mappings Lightning page.
  2. Navigate to the relevant field mapping components, and select the field type that contains the relationship you want to edit mappings for from the list view.
  3. To make changes to an existing mapping, click and click Edit.
  4. Click Save. The changes to the mapping are now saved.
Note: The new Certinia Help Mappings Lightning page allows you to edit mappings on the PSA field to a Jira Issue field, but you can also manually edit mappings for PSA Task to Jira Issue in the Setup.

Editing Jira Custom Fields Available When Mapping to Jira Issues using Custom Metadata Types

To edit mappings:

  1. In Setup, click Custom Code | Custom Metadata Types.
  2. Next to PSA to Jira Issue Fields, click Manage Records. A list of existing Jira fields displays. For a description of all the available fields and the accepted values, see Mapping PSA Direct for Jira Fields .
  3. Find the field you want to edit and click edit. For example, customfield_101010.
  4. Next to Jira Field ID, enter customfield_#####.
  5. Leave the remaining values unchanged.
  6. Click Save. The changes to the mapping are now saved.

Example - Map Jira Issue Parent Link Field, Epic Link, and Epic Name Fields

The following example contains the necessary steps for editing the existing mappings for the Sync Project Tasks from PSA to Issues in Jira or PSA Project from PSA to Issue workflow. The mappings are provided without the names of the custom fields in Jira. You must manually enter the values.

The mappings are used in the following cases:

  • Parent Link Field is used to link a standard issue type to a parent whose type is not Epic.
  • Epic Link is used to link a standard issue type to a parent whose type is Epic.
  • Epic Name is a required field when creating an issue of type Epic.
Notes:
  • In Jira Server. we assume that you have obtained the IDs of the three fields in Jira. In our case, the IDs are:
    • customfield_10701 for Parent Link Issue Field
    • customfield_10101 for Epic Link
    • customfield_10103 for Epic Name
  • In Jira Cloud, you only need to obtain the ID of customfield_10103 for Epic Name and copying IDs of customfield_10701 for Parent Link Issue Field and customfield_10101 for Epic Link are optional.
  1. From Setup, click Custom Code | Custom Metadata Types.
  2. Next to PSA to Jira Issue Field, click Manage Records. A list of existing mappings displays. For a description of all the available fields and the accepted values, see Mapping PSA Direct for Jira Fields .
  3. Next to customfield_10701 Parent Link, click Edit.
  4. In the Jira Field ID, update the Jira field ID based on the ID reflected in Jira. For example, enter customfield_10109.
  5. Leave the remaining values unchanged.
  6. Click Save. The changes to the mapping are now saved.
  7. Next to customfield_10101 Epic Link, click Edit.
  8. In the Jira Field ID, update the Jira field ID based on the ID reflected in Jira. For example, enter customfield_10014.
  9. Click Save. The changes to the mapping are now saved.
  10. Next to customfield_10103 Epic Name, click Edit.
  11. In the Jira Field ID, update the Jira field ID based on the ID reflected in Jira. For example, enter customfield_10011.
  12. Click Save. The changes to the mapping are now saved.