Issue Summary
When date/time values are stored in a JSM paragraph (rich text) field, they are rendered in raw UTC format with 24-hour time (for example, 2026-07-02 06:00 UTC) instead of preserving the customer-friendly localized format. This occurs because paragraph fields store raw text rather than structured date objects, so no timezone conversion or clock-format preference is applied at display time. This is a known, by-design behavior in JSM.
Request: Enable a configurable option for paragraph fields to select the displayed timezone (customer local, agent local, or UTC) and clock format (12-hour AM/PM or 24-hour).

Steps to Reproduce
In a JSM project, create or use an existing paragraph (rich text) field on a request type.
Have a customer submit a request that includes a date/time value (for example, 11:00 AM CST).
Use automation or manual entry to write that date/time into the paragraph field.
View the request from the customer portal or agent view.
Observe that the date/time is displayed as raw UTC in 24-hour format (for example, 2026-07-02 17:00 UTC), regardless of the customer's or agent's locale settings.
Expected Results
• The date/time value in the paragraph field should display in the customer's local timezone and preferred clock format (12-hour or 24-hour).
• Alternatively, administrators should have the ability to configure how date/time values render within paragraph fields, with options for:
Timezone: Customer local / Agent local / UTC
Clock format: 12-hour (AM/PM) / 24-hour
• The platform's existing locale and timezone preferences should apply to date tokens embedded in paragraph fields at render time.

Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available.