Getting out of range date value

Hi, team
We are using the get call of the issue endpoint. We observed the value of the nested field created under the fields/attachment/0 path as 51524-06-08T14:46:42.000-0400. We are facing a transform error for this date value as a year is out of range(invalid data). Can you please confirm that this is from an API side issue or that some user would have edited this value?

Hi @PrijenKhokhani ,

In order to get proper context of the issue, are you working on Jira Server or Jira Cloud (the tags says both and that should not be the case)?

The link you gave is an old reference to Jira Cloud REST API docs which is no longer updated. For the latest Jira Cloud REST API docs, you can check it here.

Can you share the response snippet that corresponds to this one? When I did a call to GET /rest/api/3/issue/{issueKey} I am getting something like the one below with the correct timestamp format

...
        "attachment":
        [
            {
                "self": "https://iragudo.atlassian.net/rest/api/3/attachment/10000",
                "id": "10000",
                "filename": "options.png",
                "author":
                {
                ...
                },
                "created": "2022-05-18T16:20:57.835+0800",
                "size": 34318,
                "mimeType": "image/png",
                "content": "https://iragudo.atlassian.net/rest/api/3/attachment/content/10000",
                "thumbnail": "https://iragudo.atlassian.net/rest/api/3/attachment/thumbnail/10000"
            }
        ]
...

Cheers,
Ian

@iragudo We are supporting both Jira Server and Jira Cloud. We know the format of the created field value. But, one of our customers getting value in the mentioned format. We do not have a whole response snippet as it is in the customer environment but we have some logs which I have attached below,

Also, I just wanted to know that is there a possibility of getting year > 9999 (python unsupported)?

Hi @PrijenKhokhani ,

Is this issue isolated to this specific customer only? I recommend that you create a bug report in the DEVHELP service desk so that we can investigate this further. In the bug report to be created, kindly indicate if this specific customer is running a server or a cloud instance, and replication steps if possible.

On a side note, in order to get the whole response, have you engaged your customer and have them try calling the Get Issue REST API as this will also help in isolating the root cause of the issue?

Cheers,
Ian