Queer Created Date Field Format in only 1 Project

[Shrikant Bijapurkar _NTT DATA_]

Only 1 project among several other projects we have on our site shows a queer created date format, as shown in the attached.

Cannot be fixed from "Look and Feel" as doing that would change the created date format for all other projects on our site.

Moreover, created date is a system field, so cannot even see it on any screen.

What could be the reason for this anomaly and how can we fix it?

[Diogo Teles · Accepted solution]

Hi!

Were these issues created within Jira or imported to Jira from a CSV or via API? Non-standard date format in the CSV could create issues like this on import. 

[Shrikant Bijapurkar _NTT DATA_]

Thanks Diogo.
These have been created within JIRA, not imported.
Appreciate your pointer though...

[Diogo Teles]

Hi Shrikant,

If the issue was not created through a third-party integration or via the Jira API, and the date format settings in Jira are correct and consistent, then it's possible that the issue was created or modified using an incorrect system clock or date/time settings on the device that was used.

If the system clock on the device is set incorrectly, this can result in incorrect timestamps being recorded when an issue is created or updated in Jira. This can cause issues to be displayed with incorrect created and updated dates, as in the case where the created date of an issue in Jira Software shows the year as 0023 while the updated date shows 2023.

To address this issue, you can try the following steps:

Check the date/time settings on the device that was used to create or modify the affected issue to ensure they are set correctly.
Verify that the system clock on the device is synchronized with a reliable time source, such as an NTP server.
Ensure that the time zone settings on the device are set correctly and match the time zone settings used in Jira.
If necessary, adjust the date and time on the device to the correct values.
Create a new issue or modify an existing issue to confirm that the issue created or updated timestamps are now showing correctly.
If the issue persists even after the above steps, it may be necessary to investigate further or contact Atlassian support for assistance.

[Shrikant Bijapurkar _NTT DATA_]

Thanks Diogo.
We will follow every step you have mentioned, and then reach out again (if needed) with our findings.

[Shrikant Bijapurkar _NTT DATA_]

Not "Accepting" the answer just yet. Pls give us a few days.

[Shrikant Bijapurkar _NTT DATA_]

Hello Diogo,

Thanks for taking time to respond on this one.

We realized that the issue has been caused due to incorrect date format chosen while importing some data in Jan-2023.
That basically messed up the format of Created date field for all data till 1-Feb-2023.

All tickets created post 1Feb2023 show correct date format.

We are now updating the date format for past data from backend.

Thanks Again.

Accepting your Answer.

May you give correct direction to more travellers like me, who lose their way in the journey. 

[Diogo Teles]

Thanks for the feedback. I'm really glad you were able to find the issue. That must have been a bit of a nightmare to diagnose. 

Best of luck to you guys! :)