Issue Summary

When a PIR is created from an incident, the Incident Created value shown in the PIR does not respect the viewer’s personal time zone settings. The incident’s own Created field correctly adjusts when the user changes their personal time zone, but the PIR’s Incident created value remains fixed (e.g., stays at 18 Dec 2025, 11:14 PM), leading to a 1-hour discrepancy between the incident and the PIR.

Steps to Reproduce

• Create an incident in a JSM project and note the Created date/time (e.g., 18 Dec 2025, 11:14 PM in timezone A).
• From that incident, create a Post‑Incident Review (PIR) and check the Incident created value in the PIR.
• In Personal settings, change your profile timezone to a different timezone (e.g., timezone B, 1 hour offset from timezone A).
• Reopen the incident and the associated PIR and compare:
  • Incident issue view → Created field
  • PIR → Incident created field

Expected Results

Both the Incident Created field and the PIR Incident created value should be rendered according to the viewer’s current personal time zone.

After changing the personal timezone, the displayed timestamps for the incident and the corresponding “Incident created” value in the PIR should both adjust consistently and remain in sync.

Actual Results

The incident’s Created field correctly adjusts to the new personal timezone (e.g., changes from 11:14 PM to 10:14 PM).

In the PIR, the Incident created value remains at the original time (e.g., 18 Dec 2025, 11:14 PM) and does not adjust to the new personal timezone.

This results in a consistent offset (e.g., 1 hour) between the incident’s Created date/time and the PIR’s Incident created value for the same incident, causing confusion and inaccurate incident summaries.

Workaround

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