{"errorMessages":[],"errors":{"customfield_14716":"Error parsing time: YYYY-MM-DDThh:mm:ss.sTZD","customfield_14717":"Error parsing time: YYYY-MM-DDThh:mm:ss.sTZD"}}
we are getting the above error..
In date customfields
"customfield_14716": "YYYY-MM-DDThh:mm:ss.sTZD", "customfield_14717": "YYYY-MM-DDThh:mm:ss.sTZD",
if we are using numeric format 2025-05-05T18:30:00.00+0000 its working . with the standard format getting above error
Jira’s REST API expects date and datetime fields in a strict ISO-8601 format, but it does not accept the literal placeholder `YYYY-MM-DDThh:mm:ss.sTZD`. That string is only a documentation example, not a valid value. For date-time custom fields (like `customfield_14716` and `customfield_14717`), Jira requires the full timestamp with a numeric time zone offset, such as `2025-05-05T18:30:00.000+0000`. If you send a different pattern—like one with alphabetic placeholders or missing milliseconds—Jira will return the “Error parsing time” message you’re seeing.
In your GitLab JSON payload, convert the timestamps to real ISO timestamps before sending.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.