Issue Summary

When a Form paragraph field is associated with a custom text-field (multi-line), it automatically adds a value to the field even if the user keeps it empty in the portal.

The value added is the structure for the paragraph but without content:

{
   "type": "doc",
   "version": 1,
   "content": []
}

This is causing problems because when configuring the request type, it is possible to add fields to the issue view using the section Hidden when empty fields. The field added on this section will be on the More Fields tab when the value is empty. However, for the tickets created through the Form, this value will never be empty because of the above structure and the field will be added to the Details section.

This is causing a misunderstanding for the customer because the field is appearing on the wrong section.

The field created from the portal:

The same field created from the Jira:

Steps to Reproduce

1. Create a new custom field Text Field (multi-line);
2. Add the field to the Hidden when empty fields in the request type -> Issue View;
3. Associate this field to a Paragraph Form field using the Linked Jira Field property;
4. Create a new request through the portal in a JSM service project.
5. Check the issue

Expected Results

When a new ticket is created from the portal and has the paragraph field empty, it should appear in the More Field section in the issue view instead of in the Details.

Actual Results

The Form paragraph field is filling the custom field with a default structure. This behavior makes the custom field appears in the Details sections instead of the More Fields.

Workaround

Open the ticket in the issue view and click on the field value to save it again. This process will refresh the field data and make it empty again.