Date value cannot be parsed: expected ISO 8601 format with time zone offset – CSV import in Jira Align

Date value cannot be parsed: expected ISO 8601 format with time zone offset – CSV import in Jira Align

Goal: successfully import PI planning dates from a CSV file that may contain dates expressed in local wall‑clock time without an explicit time‑zone offset, while preserving correct UTC storage and UI display according to each user’s profile time zone.

Constraint: the import engine currently rejects any date string lacking an offset, throwing the error “Date value cannot be parsed: expected ISO 8601 format with time zone offset”. This can cause off‑by‑one day shifts during daylight‑saving transitions if the source file uses local time.

• Should the import engine be modified to infer the user’s profile time zone when an offset is missing?
• Would it be preferable to require the CSV author to supply an explicit offset and provide a clear validation message instead?
• Could a fallback mode be added that treats missing‑offset values as UTC, with an optional conversion step based on the importer’s time zone?