Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

we are trying to automate the deployment notification through Gitlab using JSON script

Johnson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 5, 2025

{"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

1 answer

0 votes
Mercy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 10, 2025

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.

Suggest an answer

Log in or Sign up to answer