When creating tickets via forms the mapped fields for custom fields are not sending correctly on webhooks

Issue Summary

When creating tickets via JSM customer portal and using forms, and there are "Linked Jira Field" in form questions (when the question maps a value to any Jira field), some custom fields are not being sent correctly on webhooks payloads when the "jira:issue_updated" webhook events are sent.

The message in the payload, for the fields are sent with content as: 

"customfield_10120":{"errorMessage":"The action performed required a logged in user. Please log in and try again.","i18nErrorMessage":{"i18nKey":"sd.admin.servicedesk.error.authenticated.user.required","parameters"...

This is reproducible on Data Center: yes

Steps to Reproduce

1. Setup a webhook destination on Jira to send a message when the issue is created/updated.
2. Create a form and in a question, map the response to save the data to any field ("LINKED JIRA FIELD")
3. Setup the form to be used in a Jira SM project.
4. Create an issue in Jira SM using the created form.

Expected Results

All webhook payloads with all fields correctly set.

Actual Results

Some custom fields mapped in the forms are seen presented in the webhook payload with an error message, as below (example from a lab):

The issue_created payload is sent correctly:

created: 2024-02-15T14:23:08.805+0000
...
customfield_10120: null
customfield_10121: null
...
description: Description test
...
summary:Summary test

However the issue_updated payload, sent right after the issue_created, presented some errors:

customfield_10120 {2}
errorMessage: The action performed required a logged in user. Please log in and try again.
...
customfield_10121 {2}
errorMessage: The action performed required a logged in user. Please log in and try again.
...
description: Description test
...
summary: Summary test
...
updated: 2024-02-15T14:23:09.171+0000
...
issue_event_type_name: issue_updated

We noticed the custom field with errorMessage can vary during this update.

Workaround

Currently there is no known workaround for this behavior using the given versions. A workaround will be added here when available.

This behavior is not seen on Jira Software and Proforma