Jira supports custom fields on tickets. This guide applies to both Atlassian Jira and Jira Service Management integrations.
Custom fields can be scoped per integration (applied across all projects) or scoped to a specific Jira project.
The Field Path (Provider) in each mapping must be the field's untranslated name as defined in Jira — for example, "Story Points" or "Due date".
- Log in to Jira as an Admin.
- Navigate to Administration (gear icon, top right) -> Issues -> Custom Fields.
- The name shown in the Name column for each field is the untranslated name to use.
When creating or editing your integration, enable the Custom Field Mappings toggle. Click + Add Custom Field Mapping to add an entry for each field you want to map. Fill in the following for each entry:
Project ID Enter * to apply the mapping to all projects, or a Jira project key (e.g., OPS) to scope it to a specific project.
Field Path (Provider) The untranslated field name found in Step 1 (e.g., Due date).
Name A unique key used to reference this field in the custom_fields object when creating or patching tickets (e.g., due_date).
Click + Add CustomFieldMapping to add additional mappings.