Creating Custom Metadata Records to Support Jira Custom Fields

The following example contains the necessary steps for creating new custom metadata records to define objects for custom fields in Jira.

Note:

• By default, PSA Direct for Jira contains Epic Link, Epic Name, and Parent Link with the package that needs to be customized based on the Jira custom fields.
• Before you start to create new custom metadata records, ensure that you have created Jira custom fields of the “Select List (single choice)” type in Jira. For more information on creating custom fields in Jira, see the Atlassian documentation.
• The supported field types include: String, MultiPicklist, Email, Picklist, TextArea, and URL.

Once you have created a custom field in Jira, we recommend that you create custom metadata type records to define objects for custom fields in Jira.

1. In Setup, click Custom Code | Custom Metadata Types.
2. Next to PSA to Jira Issue Field, click Manage Records. A list of existing mappings is displayed.
3. Click New. The new custom record page displays to create a custom field.
   1. Next to Label. Enter one of the following:
      1. Fields-Industry when the field type is TextArea and Single PickList.
      2. Multipick when the field type is MultiPicklist.
   Once you move to the next field, the PSA to Jira Issue Field Name automatically populates.
4. Next to Jira Field ID. Enter one of the following:
   1. For Fields-Industry, enter customfield_10110.
   2. For Multipick, enter customfield_10909.
5. Next to Jira Field Name.
   1. For Fields-Industry, enter Industry.
   2. For Multipick, enter MultiPicklist.
6. Next to Owning Type. For example, enter fields.
7. Next to Jira Datatype. For example, enter one of the following:
   1. customfield_10110 when the field type is TextArea and Single PickList.
   2. customfield_10909.arrayFirst when the field type is MultiPicklist.
Note: This Jira Datatype must be the same as Jira Field ID. If it fails to match, then PSA to Jira synchronization or vice-versa would not work for complex fields from Jira such as drop-downs.
8. Select the Is Available for Mapping checkbox to make the field available for mapping.
9. Select the Override Field Mapping checkbox to allow users to override the mapping for this field. By default, it is selected.
10. Click Save. The new custom metadata record mapping field is now created.
11. Create a new custom record for a field that contains custom values such as drop-downs.
    1. Next to Label. For example, enter one of the following:
       1. Industry - Value when the field type is TextArea and Single PickList
       2. Multipick_value when the field type is MultiPicklist.
    2. Once you move to the next field, the PSA to Jira Issue Field Name automatically populates.
    3. Next to Jira Field ID. For example, enter value.
    4. Next to Jira Field Name. For example, enter one of the following:
       1. Value when the field type is TextArea and Single PickList
       2. Multipick_value when the field type is MultiPicklist.
    5. Next to Owning Type. For example, enter one of the following:
       1. Industry when the field type is TextArea and Single PickList
       2. customfield_10909.arrayFirst when the field type is MultiPicklist.
    6. Next to Jira Datatype. For example, enter string.
    7. Select the Is Available for Mapping checkbox to make the field available for mapping.
    8. Select the Override Field Mapping checkbox to allow users to override the mapping for this field. By default, it is selected.
12. Click Save. The new custom metadata record mapping is now created.
Note:

After custom metadata records are created, you must check whether you want to map the values to the existing field or create a new field for mapping. For more information, see Creating a New Mapping.

To support the complex differences between field values in PSA and Jira or vice-versa, the integration transforms the values from one application before syncing them with the other. If the field values are different, you must create a data transformation table.

Note that PSA to Jira or vice-versa values will differ between different projects, depending on the values are defined. The integration comes with a predefined set of mappings. We recommend that you customize the predefined mappings to avoid errors when syncing from one system to the other. To create a new mapping from Jira to PSA or vice-versa, see Creating a New Mapping.

For more information on the predefined mappings, see Customizing PSA Direct for Jira Field Mappings.

Depending on how you set up the PSA Direct for Jira, your PSA projects might be synchronized to Jira projects or vice-versa. When creating a Jira Issue, you must manually add the Jira custom field to Jira project and Jira project screens. Select the Jira custom field value, depending on the type of custom field you want to create. For example, select "primary."

The integration automatically creates a PSA project task for the Jira issue or vice-versa. Once the synchronization finishes, the Jira custom field populates with the value of the issue in Jira. For more information, see Synchronizing PSA Information to Jira .