Issue Summary

When configuring a Sync rule to create a Jira ticket, attempting to provide a value for any Number Type custom field causes the request to fail and prevents the Sync rule from being saved. The system incorrectly passes the numerical value as a string within the payload, resulting in a validation compatibility error.

Steps to Reproduce

1. Navigate to the Sync configuration and set up a rule to create a Jira ticket.

1. Map a value to a custom field of Number type (e.g., entering 2).

1. Attempt to save the Sync rule.

Expected Results

The Sync rule should save successfully. The underlying API payload for the number custom field should pass the value as an integer/numeric type, like this:
JSON

customfield_10004: { "value": 2 }

Actual Results

The Sync rule fails to save, and the UI displays the following validation error:

Provided value for: <custom field name> does not compatible with: number

An inspection of the browser's Network tab reveals that the outgoing payload wraps the numeric value in quotes, sending it as a string:
JSON
{{}}

customfield_10118: { "value": "2" }

{{}}

Workaround

Use automation rule to set the value in the field as soon as Jira ticket is created by the Sync. However, this would consume automation execution limit everytime the performs an action. https://support.atlassian.com/cloud-automation/docs/view-your-automation-usage/