interface CustomFieldPayload {
    cfType?: string;
    description?: string;
    name?: string;
    onConflict?: "USE" | "NEW" | "FAIL";
    pcri?: ProjectCreateResourceIdentifier;
    searcherKey?: string;
}

Properties

cfType?: string

The type of the custom field

Seehttps://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-fields/#api-rest-api-3-field-post `type` for values
description?: string

The description of the custom field

Thisis a custom field
name?: string

The name of the custom field

MyCustom Field
onConflict?: "USE" | "NEW" | "FAIL"

The strategy to use when there is a conflict with an existing custom field. FAIL - Fail execution, this always needs to be unique; USE - Use the existing entity and ignore new entity parameters

Every project-created entity has an ID that must be unique within the scope of the project creation. PCRI (Project Create Resource Identifier) is a standard format for creating IDs and references to other project entities. PCRI format is defined as follows: pcri:\[entityType\]:\[type\]:\[entityId\] entityType - the type of an entity, e.g. status, role, workflow type - PCRI type, either id - The ID of an entity that already exists in the target site, or ref - A unique reference to an entity that is being created entityId - entity identifier, if type is id - must be an existing entity ID that exists in the Jira site, if ref - must be unique across all entities in the scope of this project template creation

pcri:permissionScheme:id:10001
searcherKey?: string

The searcher key of the custom field

Seehttps://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-fields/#api-rest-api-3-field-post `searcherKey` for values